> Date: Mon, 11 Dec 2006 22:52:59 +0100 > From: Lennart Borgman <[EMAIL PROTECTED]> > CC: "Deutsch, Will" <[EMAIL PROTECTED]>, [EMAIL PROTECTED], > emacs-pretest-bug@gnu.org > > > > Lennart, can you tell why you asked for that, and what does it have to > > do with the original problem? > > (Did I explain why before? I think I missed it.)
No, you didn't explain this before. > In a cmd.exe console window you can actually do things like > > C:\> dir "c:/path/to/my/files/dir/" > > It works as long as the last component is not a file instead of a > directory. Then it fails. I did not notice that last case when I tested > so I believed it worked in all cases on w2k, that is why I asked Will to > test. So, yes, it was a useless test unfortunately ;-) > > Now I am just waiting for Will's report with using my patched version of > emacsclient.exe where I have changed path to Emacs bin dir to use only \ > before calling CreateProcess. I don't see why this should matter, since the Windows API groks both forward and backslashes, AFAIK. But if you think this could be the problem, how about writing a short program that uses CreateProcess, similarly to emacsclient, to start a program whose name it gets via the command line? Then Will and others could try that program with various variants of file names using different mixes of forward and back-slashes, and see if that matters at all. _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug