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

[Juanma Barranquero]

On Nov 26, 2007 5:43 PM, Stefan Monnier <address@hidden> wrote:

> > process-lines: c:/bin/gnuwin32/bin/find.exe exited with status 1
> > process-lines: c:/bin/msys/bin/find.exe exited with status 1
>
> > This is with MSYS' find ("GNU find version 4.1") and GnuWin32's find
> > ("GNU find version 4.2.20").
>
> I have no idea what this means.  Could you expand on it?

I'm not sure what are you referring to. check-declare-directory calls
find. I've tested it with GNU find, versions 4.1 (the one included
with the newest release of MSYS, which itself is related to MinGW, see
http://www.mingw.org) and version 4.2.20 (the one in the GnuWin32
project, see http://gnuwin32.sourceforge.net). Both fail.

If I manually execute

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

I get:

  c:\bin\gnuwin32\bin\find.exe: paths must precede expression
  Usage: c:\bin\gnuwin32\bin\find.exe [-H] [-L] [-P] [path...] [expression]

or

  /usr/bin/find: paths must precede expression
  Usage: /usr/bin/find [path...] [expression]

> Why would you want to wrap them?  They're not passed to a shell!

Passing "*" or "*.el" to -name fails as above. Passing ".el" or almost
anything else finishes (with 0 and no files). So there's something
fishy with the wildcard.

             Juanma