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

["Lennart Borgman (gmail)" <lennart.borgman@gmail.com>]

Eli Zaretskii wrote:
>> Date: Mon, 26 Nov 2007 23:16:05 +0100
>> From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
>> CC: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org
>>
>> Actually the two calls below
>>
>>     find -name "[ni]*.el"
>>     find -name [ni]*.el
>>
>> both works for me when I run them in cmd.exe.
> 
> That's because the unquoted wildcard [ni]*.el does not match anything
> when the startup code tries to expand it.  Such a wildcard is passed
> unaltered to the `find's `main' function, which has the same effect as
> if it were quoted.
> 
>> The case that fails is
>>
>>     find -name *.el
> 
> Because *.el matches something.

But

   find -name m*.el

also matches something and it works. Is perhaps m*.el still passed 
unaltered? This should explain the differences I see then.