|Subject:||Re: Patch to allow -nw to runemacs on w32|
|Date:||Wed, 15 Nov 2006 15:22:00 +0000|
|User-agent:||Thunderbird 188.8.131.52 (Windows/20061025)|
Lennart Borgman wrote:
In some situations you may want to be able to use the -nw option with runemacs.exe. All other options to emacs can be given to runemacs, but -nw currently gives a fatal error. The attached patch fixes this.
I don't see any error, OTOH, it launches emacs in a hidden console that you cannot get at, so isn't much use.
I don't see any reason why someone would want to use runemacs to launch emacs -nw, since the sole purpose of runemacs is to suppress the console window when launching emacs from an icon on Windows, so I don't think this needs fixing urgently. If we are going to fix this though, it would be better if emacs was run in the same console window rather than launching another one, as the latter may not be an option if the user is using telnet/ssh, or a full screen command prompt. Also we need to handle --no-window-system and the case where no GUI is available as well as -nw.
|[Prev in Thread]||Current Thread||[Next in Thread]|