bug#549: emacsclient or emacsclientw not waiting in Windows

[Vesa Suontama]

Hi,

I checked the source code for emacsclient, and it is already full of
ifdefs for windows, one more will not do any harm :)

There could be a quite easy way to make emacsclientw to behave like
emacsclient.exe if it was started from command line, just by attaching
into the console of the calling process. If the process was not
started by console, then do not create console at all, right?

The problem is that I do not have the compilation environment set up.
If I run into too big problems with that, I may not have time.

Vesa


On Tue, Jul 15, 2008 at 11:15 AM, Jason Rumney <jasonr@gnu.org> wrote:
>
>>> It works like this: have emacsclient.com and emacsclient.exe, where
>>> new emacsclient.exe is the old emacsclientw.exe, and emacsclient.com
>>> is just a wrapper that calls the emacsclient and waits for it to
>>> finish (e.g. by using a named event, which emacsclient.com waits).
>>>
>>> The other way around could be to use "AttachConsole" etc. from
>>> emacsclientw (and rename it to emacsclient), but all this is just
>>> guessing
>>> as I do not know the real reason for emacsclientw.
>
> These might be good ideas if Emacs was a Windows program. But since
> Emacs is a cross platform program, it is better to keep emacsclient the
> same as other platforms, and have emacsclientw, which is built from
> identical source code with different compiler switches, to work around
> the deficiency in Windows where it insists on making a console visible
> when you start a console program from the GUI.
>
>