Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    I don't know if it's related to your problem specifically, but you should quote the -name patterns e.g. -name '*.cs' and similar arguments when you run find. Otherwise the shell may expand the glob to a list of matching files from the current directory. Quoting ensures that *.cs is passed unexpanded to find. Commented May 7, 2014 at 22:44
  • I meant to add that. Does it matter if I use single quotes or double quotes? Either way it doesn't change the error. Commented May 7, 2014 at 22:49
  • Stop playing with quotes, while using bash arrays. See my answer! Commented May 8, 2014 at 0:53
  • @steeldriver I think the problem is reverse: There too much quotes. Commented May 8, 2014 at 1:00