Juanma Barranquero wrote:
On 12/7/06, Deutsch, Will <[EMAIL PROTECTED]> wrote:
Is this an issue with the EmacsW32 distribution? Do I need to take it up
with them or build my own?
emacsclient.exe running runemacs.exe is an issue with the EmacsW32
distribution; it's better to talk to them.
Ok, I should be responsible for EmacsW32 I guess.
Will, exactly what packages from EmacsW32 have you tried? I want the
name of the setup files. I might have made some mistake. I often check
my patches with the unpatched version first. I should not upload those
tests of course, but I might have done that by mistake. (Eh, I have to
put in some test in my routines so this does not happen.)
I suspect MS changed or removed the code that allows the file path
code to
resolve / and \ that same.
It would be useful if you could try with the standard distribution
(from CVS) to determine whether there's any issue with / vs. \.
The unpatched version should really be the just the standard
distribution (from CVS) compiled + optionally the EmacsW32 files but
those should not be involved here at all.
On 12/6/06, Deutsch, Will <[EMAIL PROTECTED]> wrote:
> > Command output of emacsclient bellow:
> > C:\Program Files (x86)\Emacs\emacs\bin>emacsclient
> > emacsclient: Can't find C:\Program Files
> > (x86)\Emacs\emacs/bin/runemacs.exe
If you copy that output and just do
C:\> dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe"
what do you get?
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
