Re: Using `call-process-shell-command' in `process-lines'

[Eli Zaretskii <eliz@gnu.org>]

> Date: Tue, 27 Nov 2007 00:04:02 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> > >>    find -name *l.el
> > >>    find -name m*.el
> > >>    find -name "*.el"
> > > 
> > > Sheer luck, the first tow ones.  You _must_ quote the wildcard to get
> > > predictable behavior.

To give you a hint: whether unquoted wildcards work or not depends on
whether files in the directory where you run the above commands do or
do not have files that match the wildcards you give to `find'.  That's
because the startup code which tries to expand wildcards leaves them
intact if they don't match anything in the current directory, which
has the same effect as quoting them.

Take for example the following command:

  find c:/emacs -name *l.el

Assuming c:/emacs is the root of the Emacs source tree, try to type
this once from the c:/emacs/lisp directory and then from a directory
that doesn't have any *.el files, and you will see different behavior
(the first one should err out).

That's why I said that you _must_ quote wildcards to get predictable
behavior from `find'.