Let me start by saying, be really-really careful with scripted rm operations. if you don't filter out enough files you'll delete stuff you didn't intend to. That being said, you can start by building the output of grep lines into a single line by piping it to 'xargs'.

ls -aFR | grep "." | grep "/" | grep "Witcher" | xargs

if you wanted to use that line as arguments to rm you could do something like this. With backticks...

rm `ls operation | xargs`

This will evaluate everything between the backticks first, resulting in the string of filenames which will then be used as the argument to rm.

I would also recommend looking at the find command. This can be used to search for files. Then the -exec option can be used to run an rm, or whatever command you desire, against the matching filenames.

Make sure you are using backticks ( the key to the left of the 1 key) around your original ls command. It sounds like you were using single and double quotes.

And xargs is present on Macs. Type...

man xargs

and you should see instructions on the xargs command.

I would encourage Brent's statement on using find in stead of other commands. Agreed that it is a bit to get use to, but it extremely useful in the long term.

It'll allow you to first check what you are about to remove then execute.

An example:

find -E ./ -regex "(\.|/|Witcher)" -exec ls -ld {} >> mydelfile \;

# Confirm the list, and now re-run with rm 

find -E ./ -regex "(\.|/|Witcher)" -exec rm -rf {} \;

The above is just an example and likely does not find the exact files you re looking for. The -E provides extended regex capabilities.