> From: Juanma Barranquero <[email protected]>
> Date: Sat, 28 Jan 2012 12:29:23 +0100
> Cc: sthfrnth <[email protected]>, [email protected]
>
> I'm also on W7 (64-bit, like the OP), and I see the problem, too.
You mean, the find.exe from my port doesn't work with quoted
wildcards?
> > emacs -Q -batch --eval "(princ (directory-files \".\" nil \"?*\\.c\\'\"))"
> >
> > If quoted arguments work "as I'd expect" (i.e. quotes are removed,
> > unless escaped by a backslash, in which case the backslash is removed
> > and the quote stays), then this command should display the list of all
> > *.c files in the directory where you invoke this command.
>
> It displays the list of .c files, as expected:
Then something was wrong with my reasoning... Hm...
If you compile the simple program below, and then type
echocmd "*find*"
what do you see? And what do you see if you type
echocmd *.c
and
echocmd "*.c"
in a directory with C files?
--------------------------- echocmd.c -----------------------
#include <stdio.h>
#include <windows.h>
int main (int argc, char *argv[])
{
int i = 0;
printf ("`%s'\n", GetCommandLine ());
while (argc--)
printf ("%d: `%s'\n", i++, *(argv++));
return 0;
}
-----------------------------------------------------------------