Thanks for the information. I will see what I can do. Maybe I will repack what I am using now (I have added some things that I have not published), but I do not have time to do much more. Then I can include the emacsclient version you have pointed me to.
On Mon, Feb 20, 2012 at 01:14, <nyc4...@aol.com> wrote: > Lennart Borgman <lennart.borg...@gmail.com> writes: > >> That is the version I am running to and I do not see the problem. >> >> I see other problems though since I am using windows 7 64-bit. >> Something the compiler did does not fit on 64-bit systems I think. >> >> What windows version are you running? (And what command prompt? I >> guess you are using cmd.exe, or?) > > I am running Microsoft Windows XP [Version 5.1.2600] > > Yes, the "Command Prompt" is cmd.exe > > The emacsclient.exe from: > > GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600) of 2009-11-03 on LENNART-69DE564 > (patched) > > > runs just fine on the W32 emacs.exe binary version: > > In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) > from trunk 2011-02-16 on LENNART-69DE564 (patched) > > >> >> I do not think I can do something about this now, but let us collect >> the information at least. ;-) >> >> >> On Sun, Feb 19, 2012 at 23:38, <nyc4...@aol.com> wrote: >>> Lennart Borgman <lennart.borg...@gmail.com> writes: >>> >>>> Thanks for the bug report nyc4bos. However I can not see this problem >>>> with the latest version of Emacs+EmacsW32 I have released. >>> >>> I guess that version I am seeing the problem with is not a >>> "released" version. >>> >>>> Could you >>>> please tell me exactly how to reproduce it? >>> >>> 1. Install EmacsW32 from: >>> >>> http://ourcomments.org/Emacs/DL/EmacsW32/test/Emacs-24-BzrP110217-EmacsW32-1.58.exe >>> >>> (the latest version I could find) which also starts an EmacsW32 instance >>> after installation. >>> >>> 2. Start a cmd prompt. The EmacsW32 instance is now "behind" the >>> "Command Prompt" window. >>> >>> 3. From the "Command Prompt" window, invoke emacsclient by typing >>> C:\Program Files\EmacsW32\emacs\bin\emacsclient.exe >>> >>> The EmacsW32 frame does not come to the forefront (it remains >>> behind the "Command Prompt" window) however, the emacs icon >>> blinks for a few seconds >>> >>> >>> If you replace step 2 (above) by running this older version of >>> EmacsW32 emacsclient.exe instead: >>> >>> GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600) of 2009-11-03 on >>> LENNART-69DE564 (patched) >>> >>> the EmacsW32 frame is raised to the forefront, as expected. >>> >>> >>> In both versions of emacsclient.exe when the EmacsW32 frame >>> is iconified, when running either emacsclient.exe from the >>> command prompt, EmacsW32 is successfully deiconified and is >>> put in the forefront (raised frame). >>> >>> >>>> >>>> On Fri, Feb 17, 2012 at 23:18, <nyc4...@aol.com> wrote: >>>>> >>>>> This is a bug report for the PATCHED Emacs+EmacsW32. >>>>> >>>>> emacsclient does not raise the frame when invoked.
