Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Wed, 13 Dec 2006 00:11:05 +0100 > From: Lennart Borgman <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED], [EMAIL PROTECTED], > emacs-pretest-bug@gnu.org > > This is for the code I have added in my patched version of emacsclient.c > to start Emacs automatically. Since I wanted to avoid errors I tested as > much as I could come up with. Some testing overkill I guess. Why not test the status returned by whatever function you use to run Emacs? If it is called to run a non-executable file, it will return an appropriate error code, right? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Eli Zaretskii wrote: Date: Tue, 12 Dec 2006 00:09:00 +0100 From: Lennart Borgman <[EMAIL PROTECTED]> It turned out that the test below for execute access failed. That seems strange since indeed runemacs.exe can be executed. Is that perhaps a bug in MinGW or in w32? Or am I misunderstanding something? Where could I try to report this (potential) bug? According to this: http://msdn2.microsoft.com/en-us/library/1w06ktdy(VS.80).aspx the Windows version of `access' doesn't support X_OK at all, only F_OK, R_OK, and W_OK. I don't really understand why did you need that test. The CVS version of emacsclient.c doesn't have such a test, AFAICS. Ah, thanks Eli. I did not know that X_OK was not supported (though somewhere in my head is a memory of hearing theis before). This is for the code I have added in my patched version of emacsclient.c to start Emacs automatically. Since I wanted to avoid errors I tested as much as I could come up with. Some testing overkill I guess. Now the automatic starting of Emacs seems to work very well on w32. If someone is interested I believe the code should run on other platforms too. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Tue, 12 Dec 2006 00:09:00 +0100 > From: Lennart Borgman <[EMAIL PROTECTED]> > > It turned out that the test below for execute access failed. That seems > strange since indeed runemacs.exe can be executed. Is that perhaps a bug > in MinGW or in w32? Or am I misunderstanding something? Where could I > try to report this (potential) bug? According to this: http://msdn2.microsoft.com/en-us/library/1w06ktdy(VS.80).aspx the Windows version of `access' doesn't support X_OK at all, only F_OK, R_OK, and W_OK. I don't really understand why did you need that test. The CVS version of emacsclient.c doesn't have such a test, AFAICS. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> 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
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Eli Zaretskii wrote: Date: Thu, 7 Dec 2006 23:55:58 -0800 From: "Deutsch, Will" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, I was specifically asked to provide the / vs \ output of Dir. Sorry, I missed that. 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.) 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. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Mon, 11 Dec 2006 19:25:59 +0100 > From: Lennart Borgman <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED], [EMAIL PROTECTED], > emacs-pretest-bug@gnu.org > > I changed my routines just a little bit so I now upload also a zip file > with nothing but precompiled Windows binaries of Emacs. However this is > straight from the CVS, not the pretest tar balls. I see no big problem > with that however. I do see a problem: we want people to try the pretest, not the CVS. For example, the recently reported problem with cus-load.el is not visible in the CVS version. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Eli Zaretskii wrote: Date: Fri, 08 Dec 2006 02:18:20 +0100 From: Lennart Borgman <[EMAIL PROTECTED]> Cc: "Deutsch, Will" <[EMAIL PROTECTED]>, emacs-pretest-bug@gnu.org On the other hand we might be receiving bug reports just because there are more users if we supply a prebuildt binary on MS Windows. It might be more important. I have no problems with having a precompiled Windows binary distro as part of the pretest, as long as it is a straight compilation of the pretest sources without any extra quirks. If you are willing to do this job, please talk to Chong Yidong and coordinate your uploads to alpha.gnu.org. I changed my routines just a little bit so I now upload also a zip file with nothing but precompiled Windows binaries of Emacs. However this is straight from the CVS, not the pretest tar balls. I see no big problem with that however. The zip file is about 50% bigger than the installer that includes both Emacs and EmacsW32. I have a new computer and better bandwidth so it is however not a problem any more. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/8/06, Eli Zaretskii <[EMAIL PROTECTED]> wrote: I have no problems with having a precompiled Windows binary distro as part of the pretest, as long as it is a straight compilation of the pretest sources without any extra quirks. If you are willing to do this job, please talk to Chong Yidong and coordinate your uploads to alpha.gnu.org. I'm willing to build precompiled binaries for Windows (pretest, and perhaps periodic builds from the CVS once the current release is out). I'll talk with Chong Yidong (unless Lennart prefers to do it himself). /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Lennart Borgman wrote: I know that it is important that many users build Emacs too, but the problem on MS Windows is that most users will not do that. That means that there will be fewer testers when we do not supply prebuilt binaries. The aim of a pretest has always been to get a limited number of testers who are technically skilled enough to give us meaningful bug reports. What we don't want during pretest is a flood of vague bug reports from the masses, because we don't have the bandwidth to deal with that. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Thu, 7 Dec 2006 23:55:58 -0800 > From: "Deutsch, Will" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>, > <[EMAIL PROTECTED]>, > > > I was specifically asked to provide the / vs \ output of Dir. Sorry, I missed that. Lennart, can you tell why you asked for that, and what does it have to do with the original problem? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, I was specifically asked to provide the / vs \ output of Dir. However, you may note that / works as long as it isn't the last element of Dir. Cheers, Will -Original Message- From: Eli Zaretskii [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 11:39 PM To: Deutsch, Will Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM > Date: Thu, 7 Dec 2006 16:59:05 -0800 > From: "Deutsch, Will" <[EMAIL PROTECTED]> > Cc: emacs-pretest-bug@gnu.org > > It appears that the / between the bin and the command is the problem. This may > be an OS bug. > > Here is the dir output: > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found Am I missing something here? How are the problems with DIR relevant to emacsclient? It is well known that DIR doesn't grok forward slashes because it tries to interpret what follows a forward slash as an option (try "DIR /?" and you will see what options it supports). However, emacsclient is not DIR; emacsclient simply passes the file names to the OS API, and the OS API does support forward slashes as well as backslashes. So please show us where the forward slashes fail inside emacsclient, not with DIR. smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Fri, 08 Dec 2006 02:18:20 +0100 > From: Lennart Borgman <[EMAIL PROTECTED]> > Cc: "Deutsch, Will" <[EMAIL PROTECTED]>, emacs-pretest-bug@gnu.org > > On the other hand we might be receiving bug reports just because there > are more users if we supply a prebuildt binary on MS Windows. It might > be more important. I have no problems with having a precompiled Windows binary distro as part of the pretest, as long as it is a straight compilation of the pretest sources without any extra quirks. If you are willing to do this job, please talk to Chong Yidong and coordinate your uploads to alpha.gnu.org. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> Date: Thu, 7 Dec 2006 16:59:05 -0800 > From: "Deutsch, Will" <[EMAIL PROTECTED]> > Cc: emacs-pretest-bug@gnu.org > > It appears that the / between the bin and the command is the problem. This > may > be an OS bug. > > Here is the dir output: > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found Am I missing something here? How are the problems with DIR relevant to emacsclient? It is well known that DIR doesn't grok forward slashes because it tries to interpret what follows a forward slash as an option (try "DIR /?" and you will see what options it supports). However, emacsclient is not DIR; emacsclient simply passes the file names to the OS API, and the OS API does support forward slashes as well as backslashes. So please show us where the forward slashes fail inside emacsclient, not with DIR. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
I'm not sure why... I'll run prebuilt binaries and test and if needed even provide basic output of debugger commands. I run App and System and HW level debuggers in the course of my job. So I'm already exposed to the machine code of EVERYTHING that is running on the system at any time. It is imposable not to be. Therefore providing feedback from a debugger in the case of exceptions or crash is no stretch. Mostly the point of my email is that due to the nature of my job I can't/wont build my own binaries from source. However, I will file detailed bugs and assist where possible in root causing the problem. Cheers, Will -Original Message- From: Nick Roberts [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 6:22 PM To: Deutsch, Will Cc: Lennart Borgman; Juanma Barranquero; emacs-pretest-bug@gnu.org Subject: RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM > I'm a software developer who works on code that I cannot contaminate. I > cannot risk even the appearance of contamination... > ...I'm happy to run binaries to test things and provide detailed > reports. I'll provide feedback and even run the debugger, minus the source, > however, I just cannot risk working directly with the source even for a > simple build situation. These two statements seem contradictory. -- Nick http://www.inet.net.nz/~nickrob smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/8/06, Deutsch, Will <[EMAIL PROTECTED]> wrote: I'm just an Emacs user not an Emacs developer... And we thank you for helping test Emacs. I really don't want to get into a free/non-free software debate. I'm already pro-free software... What Lennart and I are debating is not a free/non-free software issue, but wasted efforts. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: And I will try to make sure that it is just the CVS code (+ EmacsW32 + the installer of course). I'm grateful that you plan on providing prebuilt binaries for testing on Windows. However, as soon as you add that parenthesis, it turns less useful, because it diverges from what we want to test. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
> I'm a software developer who works on code that I cannot contaminate. I > cannot risk even the appearance of contamination... > ...I'm happy to run binaries to test things and provide detailed > reports. I'll provide feedback and even run the debugger, minus the source, > however, I just cannot risk working directly with the source even for a > simple build situation. These two statements seem contradictory. -- Nick http://www.inet.net.nz/~nickrob ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, I'm just an Emacs user not an Emacs developer... However, here is my feedback on this issue. I'm a software developer who works on code that I cannot contaminate. I cannot risk even the appearance of contamination. Therefore, I don't download and compile anything right now. I don't even use source debs or srpms on my linux boxes. Past jobs were more GPL friendly, so I gladly download and compiled everything. When my job changes I will gladly go back to building from CVS. I'm happy to run binaries to test things and provide detailed reports. I'll provide feedback and even run the debugger, minus the source, however, I just cannot risk working directly with the source even for a simple build situation. Were the world perfect someone would pay me to work on GPL code. However, currently I'm being paid to work on something else. I really don't want to get into a free/non-free software debate. I'm already pro-free software... Cheers, Will -Original Message- From: Lennart Borgman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 6:00 PM To: Juanma Barranquero Cc: Deutsch, Will; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM Juanma Barranquero wrote: > On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: > >> On the other hand we might be receiving bug reports just because there >> are more users if we supply a prebuildt binary on MS Windows. It might >> be more important. > > Pretesters should be able to build their own Emacs, IMHO. There are > official (or mostly official) binary builds of Emacs for Windows, once > it is released. I know that it is important that many users build Emacs too, but the problem on MS Windows is that most users will not do that. That means that there will be fewer testers when we do not supply prebuilt binaries. For this reason I have planned to supply more prebuilt binaries during the pretest. (They will not be from the tarball, but directly from the CVS.) And I will try to make sure that it is just the CVS code (+ EmacsW32 + the installer of course). smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Yeah, no problem. Cheers, Will -Original Message- From: Lennart Borgman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 6:03 PM To: Deutsch, Will Cc: Juanma Barranquero; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM I will change the slashes to forward slashes only as soon as I have time. Could you test when I have done that Will? smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
I will change the slashes to forward slashes only as soon as I have time. Could you test when I have done that Will? ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Juanma Barranquero wrote: On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: On the other hand we might be receiving bug reports just because there are more users if we supply a prebuildt binary on MS Windows. It might be more important. Pretesters should be able to build their own Emacs, IMHO. There are official (or mostly official) binary builds of Emacs for Windows, once it is released. I know that it is important that many users build Emacs too, but the problem on MS Windows is that most users will not do that. That means that there will be fewer testers when we do not supply prebuilt binaries. For this reason I have planned to supply more prebuilt binaries during the pretest. (They will not be from the tarball, but directly from the CVS.) And I will try to make sure that it is just the CVS code (+ EmacsW32 + the installer of course). ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, I just did the dir test on Server 2003SP1... It seems DIR on 2003SP1 and Vista behave the same yet the exec doesn't. 2003SP1: Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. D:\Documents and Settings\wdeutsch>dir "D:\Program Files\Emacs\emacs/bin/runemac s.exe" Volume in drive D is System Disk Volume Serial Number is 10CF-7D40 Directory of D:\Program Files\Emacs\emacs\bin File Not Found D:\Documents and Settings\wdeutsch>dir "D:\Program Files\Emacs\emacs/bin\runemac s.exe" Volume in drive D is System Disk Volume Serial Number is 10CF-7D40 Directory of D:\Program Files\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 9,976,893,440 bytes free D:\Documents and Settings\wdeutsch>dir "D:\Program Files\Emacs\emacs\bin\runemac s.exe" Volume in drive D is System Disk Volume Serial Number is 10CF-7D40 Directory of D:\Program Files\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 9,976,893,440 bytes free D:\Documents and Settings\wdeutsch>dir "D:/Program Files/Emacs/emacs/bin/runemac s.exe" Volume in drive D is System Disk Volume Serial Number is 10CF-7D40 Directory of D:\Program Files\Emacs\emacs\bin File Not Found D:\Documents and Settings\wdeutsch>dir "D:/Program Files/Emacs/emacs/bin\runemac s.exe" Volume in drive D is System Disk Volume Serial Number is 10CF-7D40 Directory of D:\Program Files\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 9,976,893,440 bytes free D:\Documents and Settings\wdeutsch> But emacsclient still works fine. Cheers, Will -Original Message- From: Lennart Borgman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 5:26 PM To: Deutsch, Will Cc: Juanma Barranquero; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM Deutsch, Will wrote: > Hi, > > It appears that the / between the bin and the command is the problem. This > may > be an OS bug. > > Here is the dir output: > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found > > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin\runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > 11/21/2006 02:00 AM46,523 runemacs.exe >1 File(s) 46,523 bytes >0 Dir(s) 109,831,647,232 bytes free > > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found ... > > It would appear MS changed the behavior of the / in the path. Could you please try with only forward slashes too? > Here are the list of images I have tried (I have installed most of these on > XP > and Server 2003SP1 x64 and x86): > Emacs-22-CvsP061121-EmacsW32-1.10.exe > Emacs-22-CvsP060830-EmacsW32-1.06.exe Those are both patched versions. The patched version as a P in the name and the unpatched has a U instead. > Sorry, the system that I did most of my Emacs installs on has been wiped and > repurposed so I no longer have a complete record. I've spot tested many > versions in between these two. > > This is what is running: > This is GNU Emacs 22.0.91.1 (i386-mingw-nt6.0.6000) > of 2006-11-20 on W2ONE I have changed this message in the latest patched version so it says that it is patched. I have also changed the icon in the patched version to make it more clear which version is used. I will update my web site soon to tell this. (Maybe I will change to a better one than the one I am using now, but I do not have time to do that at the moment.) smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Deutsch, Will wrote: Hi, I only had the install files left around from the patched files. However, I have tried in unpatched, I just don't have the install source as the drive from that system image was wiped. I definitely understand the difference between the patched and unpatched versions. However, for this issue I saw no difference. Thanks, I see. Here is more dir output: C:\Users\wdeutsch>dir "C:/Program Files (x86)/Emacs/emacs/bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found C:\Users\wdeutsch>dir "C:/Program Files (x86)/Emacs/emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 109,375,385,600 bytes free Those two really makes me believe it is an OS bug. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, I only had the install files left around from the patched files. However, I have tried in unpatched, I just don't have the install source as the drive from that system image was wiped. I definitely understand the difference between the patched and unpatched versions. However, for this issue I saw no difference. Here is more dir output: Microsoft Windows [Version 6.0.6000] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 109,375,385,600 bytes free C:\Users\wdeutsch>dir "C:/Program Files (x86)/Emacs/emacs/bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found C:\Users\wdeutsch>dir "C:/Program Files (x86)/Emacs/emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 12/05/2006 02:22 AM29,115 runemacs.exe 1 File(s) 29,115 bytes 0 Dir(s) 109,375,385,600 bytes free C:\Users\wdeutsch> Cheers, Will Deutsch -Original Message- From: Lennart Borgman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 5:26 PM To: Deutsch, Will Cc: Juanma Barranquero; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM Deutsch, Will wrote: > Hi, > > It appears that the / between the bin and the command is the problem. This > may > be an OS bug. > > Here is the dir output: > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found > > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin\runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > 11/21/2006 02:00 AM46,523 runemacs.exe >1 File(s) 46,523 bytes >0 Dir(s) 109,831,647,232 bytes free > > C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin/runemacs.exe" > Volume in drive C is OS Drive > Volume Serial Number is 8020-54D6 > > Directory of C:\Program Files (x86)\Emacs\emacs\bin > > File Not Found ... > > It would appear MS changed the behavior of the / in the path. Could you please try with only forward slashes too? > Here are the list of images I have tried (I have installed most of these on > XP > and Server 2003SP1 x64 and x86): > Emacs-22-CvsP061121-EmacsW32-1.10.exe > Emacs-22-CvsP060830-EmacsW32-1.06.exe Those are both patched versions. The patched version as a P in the name and the unpatched has a U instead. > Sorry, the system that I did most of my Emacs installs on has been wiped and > repurposed so I no longer have a complete record. I've spot tested many > versions in between these two. > > This is what is running: > This is GNU Emacs 22.0.91.1 (i386-mingw-nt6.0.6000) > of 2006-11-20 on W2ONE I have changed this message in the latest patched version so it says that it is patched. I have also changed the icon in the patched version to make it more clear which version is used. I will update my web site soon to tell this. (Maybe I will change to a better one than the one I am using now, but I do not have time to do that at the moment.) smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: On the other hand we might be receiving bug reports just because there are more users if we supply a prebuildt binary on MS Windows. It might be more important. Pretesters should be able to build their own Emacs, IMHO. There are official (or mostly official) binary builds of Emacs for Windows, once it is released. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Deutsch, Will wrote: Hi, It appears that the / between the bin and the command is the problem. This may be an OS bug. Here is the dir output: C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 11/21/2006 02:00 AM46,523 runemacs.exe 1 File(s) 46,523 bytes 0 Dir(s) 109,831,647,232 bytes free C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found ... It would appear MS changed the behavior of the / in the path. Could you please try with only forward slashes too? Here are the list of images I have tried (I have installed most of these on XP and Server 2003SP1 x64 and x86): Emacs-22-CvsP061121-EmacsW32-1.10.exe Emacs-22-CvsP060830-EmacsW32-1.06.exe Those are both patched versions. The patched version as a P in the name and the unpatched has a U instead. Sorry, the system that I did most of my Emacs installs on has been wiped and repurposed so I no longer have a complete record. I've spot tested many versions in between these two. This is what is running: This is GNU Emacs 22.0.91.1 (i386-mingw-nt6.0.6000) of 2006-11-20 on W2ONE I have changed this message in the latest patched version so it says that it is patched. I have also changed the icon in the patched version to make it more clear which version is used. I will update my web site soon to tell this. (Maybe I will change to a better one than the one I am using now, but I do not have time to do that at the moment.) ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Juanma Barranquero wrote: On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: Ok, I should be responsible for EmacsW32 I guess. Yes, I think so. And this report is exactly the kind of thing some people in the list were talking about: we're receiving a bug report for a problem that it is perhaps non-existent in the official builds. On the other hand we might be receiving bug reports just because there are more users if we supply a prebuildt binary on MS Windows. It might be more important. 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. As long as it is not the standard tarball or straight from the CVS, I would count it as unofficial. Differences can creep in. It would be very nice if there were un official prebuilt binary package for MS Windows. Of course mistakes could happen there too, but I think they will be sorted out rather quickly. In the case of the EmacsW32 distros I actually think the same though they do not have any official status of course. ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/8/06, Lennart Borgman <[EMAIL PROTECTED]> wrote: Ok, I should be responsible for EmacsW32 I guess. Yes, I think so. And this report is exactly the kind of thing some people in the list were talking about: we're receiving a bug report for a problem that it is perhaps non-existent in the official builds. 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. As long as it is not the standard tarball or straight from the CVS, I would count it as unofficial. Differences can creep in. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, It appears that the / between the bin and the command is the problem. This may be an OS bug. Here is the dir output: C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 11/21/2006 02:00 AM46,523 runemacs.exe 1 File(s) 46,523 bytes 0 Dir(s) 109,831,647,232 bytes free C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs\bin/runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin File Not Found C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs\emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 11/21/2006 02:00 AM46,523 runemacs.exe 1 File(s) 46,523 bytes 0 Dir(s) 109,831,528,448 bytes free C:\Users\wdeutsch>dir "C:\Program Files (x86)\Emacs/emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 11/21/2006 02:00 AM46,523 runemacs.exe 1 File(s) 46,523 bytes 0 Dir(s) 109,831,528,448 bytes free C:\Users\wdeutsch>dir "C:\Program Files (x86)/Emacs/emacs/bin\runemacs.exe" Volume in drive C is OS Drive Volume Serial Number is 8020-54D6 Directory of C:\Program Files (x86)\Emacs\emacs\bin 11/21/2006 02:00 AM46,523 runemacs.exe 1 File(s) 46,523 bytes 0 Dir(s) 109,830,873,088 bytes free C:\Users\wdeutsch> It would appear MS changed the behavior of the / in the path. Here are the list of images I have tried (I have installed most of these on XP and Server 2003SP1 x64 and x86): Emacs-22-CvsP061121-EmacsW32-1.10.exe Emacs-22-CvsP060830-EmacsW32-1.06.exe Sorry, the system that I did most of my Emacs installs on has been wiped and repurposed so I no longer have a complete record. I've spot tested many versions in between these two. This is what is running: This is GNU Emacs 22.0.91.1 (i386-mingw-nt6.0.6000) of 2006-11-20 on W2ONE I've run both the patched an unpatched releases. Cheers, Will -Original Message- From: Lennart Borgman [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 4:36 PM To: Juanma Barranquero Cc: Deutsch, Will; emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM 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? smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
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 emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
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. 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. \. /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, No, I'm not using alternate editor nor and I using -a... I actually tried setting ALTERNATE_EDITOR Is this an issue with the EmacsW32 distribution? Do I need to take it up with them or build my own? I know this distribution works fine on Server 2003, Server 2003 x64, XP Pro, and XP Pro x64. Vista x64 is the only place that has this problem. I suspect MS changed or removed the code that allows the file path code to resolve / and \ that same. Cheers, Will -Original Message- From: Juanma Barranquero [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 10:41 AM To: Deutsch, Will Cc: emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM On 12/7/06, Deutsch, Will <[EMAIL PROTECTED]> wrote: > I'm using a 3rd party distribution from: > http://ourcomments.org/Emacs/EmacsW32.html (EmacsW32 site) I suspected as much. > I've tried both their patched and unpatched Emacs distribution. Are you using the ALTERNATE_EDITOR environment variable? Because the emacsclient.exe from the unpatched distribution shouldn't try to execute runemacs.exe *at all*, unless you're doing C:\yourpath\emacsclient -a runemacs.exe my-file.txt /L/e/k/t/u smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
On 12/7/06, Deutsch, Will <[EMAIL PROTECTED]> wrote: I'm using a 3rd party distribution from: http://ourcomments.org/Emacs/EmacsW32.html (EmacsW32 site) I suspected as much. I've tried both their patched and unpatched Emacs distribution. Are you using the ALTERNATE_EDITOR environment variable? Because the emacsclient.exe from the unpatched distribution shouldn't try to execute runemacs.exe *at all*, unless you're doing C:\yourpath\emacsclient -a runemacs.exe my-file.txt /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
RE: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
Hi, I'm using a 3rd party distribution from: http://ourcomments.org/Emacs/EmacsW32.html (EmacsW32 site) I've tried both their patched and unpatched Emacs distribution. Cheers, Will -Original Message- From: Juanma Barranquero [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 10:31 AM To: Deutsch, Will Cc: emacs-pretest-bug@gnu.org Subject: Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM 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 Are you compiling Emacs from a prerelease tarball, from the CVS or perhaps a third-party distribution? /L/e/k/t/u smime.p7s Description: S/MIME cryptographic signature ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
Re: emacsclient and emacsclientw don't work in Windows Vista x64 RTM
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 Are you compiling Emacs from a prerelease tarball, from the CVS or perhaps a third-party distribution? /L/e/k/t/u ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
emacsclient and emacsclientw don't work in Windows Vista x64 RTM
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 C:\Program Files (x86)\Emacs\emacs\bin> Emacsclientw has the same output only in a dialog box. I have run usethis.exe several times in an attempt to trick runemacs to use \ instead of the / it is using. This behavior is consistent across several versions of Gnu Emacs I have tested. (This doesn't seem to be a regression.) In GNU Emacs 22.0.91.1 (i386-mingw-nt6.0.6000) of 2006-11-20 on W2ONE X server distributor `Microsoft Corp.', version 6.0.6000 configured using `configure --with-gcc (3.4) --cflags -Id:/g/include' Important settings: value of $LC_ALL: nil value of $LC_COLLATE: nil value of $LC_CTYPE: nil value of $LC_MESSAGES: nil value of $LC_MONETARY: nil value of $LC_NUMERIC: nil value of $LC_TIME: nil value of $LANG: ENU locale-coding-system: cp1252 default-enable-multibyte-characters: t Major mode: Lisp Interaction Minor modes in effect: encoded-kbd-mode: t tooltip-mode: t tool-bar-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t unify-8859-on-encoding-mode: t utf-translate-cjk-mode: t auto-compression-mode: t line-number-mode: t Recent input: M-x r e p o r t b u g - Recent messages: (C:\Program Files (x86)\Emacs\emacs\bin\emacs.exe) Loading encoded-kb...done Adding c:/Program Files (x86)/Emacs/EmacsW32/lisp/ to load-path Loading cl-macs...done Loading cl-seq...done Loading easy-mmode...done For information about the GNU Project and its goals, type C-h C-p. [2 times] Loading emacsbug... Loading regexp-opt...done Loading emacsbug...done ___ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
