Re: Patch to allow -nw to runemacs on w32

[Jason Rumney]

Lennart Borgman wrote:
> The situation where I thought the current behaviour was a problem was 
> when specifying --alternate-editor to emacsclient. If the user for 
> some reason (which I might not understand ;-) wants to run emacs in a 
> console, and this should be started through the use of 
> --alternate-editor then the simplest way (from a user perspective) to 
> get this working might be to do something like
>
>    set alternate_editor=runemacs.exe -nw

The simplest way is emacs -nw. Why would they use runemacs? If they are 
used to running emacs -nw, then they would have learnt quickly that 
runemacs is not suitable.