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

[Stefan Monnier]

> If this minor variant works:

>    (apply #'call-process "c:/bin/gnuwin32/bin/find.exe" nil
>      (get-buffer-create "output") nil '("c:/emacs/trunk/lisp/" "-name"
>      (shell-quote-argument "*.el")))

> it might give you a clue to the solution.  The call to
> shell-quote-argument should be limited to Windows only, since the
> Windows implementation of the library function called by call-process
> constructs a single command line out of all arguments, which of course
> means you need an extra pair of quotes.

But this library function already does the necessary quoting.
The problem seems to be that under Windows, the globbing is not done by
the shell but by the application, so while under Unix no globbing is
performed (because no shell is involved) under Windows `find'
performs globbing.

I'd be surprised if it's the first time this happens.  What solutions
have we used in the other cases where this problem showed up?


        Stefan