On Sat, Jan 28, 2012 at 13:04, Eli Zaretskii <e...@gnu.org> wrote:

> You mean, the find.exe from my port doesn't work with quoted
> wildcards?

Yes.

C:\emacs\trunk\lisp> \bin\ezwt\bin\find.exe . -name *find*
\bin\ezwt\bin\find.exe: paths must precede expression
Usage: \bin\ezwt\bin\find.exe [-H] [-L] [-P] [path...] [expression]

C:\emacs\trunk\lisp> \bin\ezwt\bin\find.exe . -name "*find*"
\bin\ezwt\bin\find.exe: paths must precede expression
Usage: \bin\ezwt\bin\find.exe [-H] [-L] [-P] [path...] [expression]

> If you compile the simple program below, and then type
>
>  echocmd "*find*"
>
> what do you see?

C:\emacs\trunk\lisp> ..\..\echocmd.exe "*find*"
`..\..\echocmd.exe "*find*"'
0: `..\..\echocmd.exe'
1: `find-cmd.el'
2: `find-cmd.elc'
3: `find-dired.el'
4: `find-dired.elc'
5: `find-file.el'
6: `find-file.elc'
7: `find-lisp.el'
8: `find-lisp.elc'
9: `finder-inf.el'
10: `finder.el'
11: `finder.elc'

>  And what do you see if you type
>
>  echocmd *.c

C:\emacs\trunk\src> ..\..\echocmd.exe *.c
`..\..\echocmd.exe *.c'
0: `..\..\echocmd.exe'
1: `alloc.c'
[... the rest of .c files in src/ ...]
113: `xterm.c'

> and
>
>  echocmd "*.c"

Same output.

    Juanma

Reply via email to