|Subject:||Re: Patch to allow -nw to runemacs on w32|
|Date:||Wed, 15 Nov 2006 23:02:33 +0100|
|User-agent:||Thunderbird 22.214.171.124 (Windows/20061025)|
Jason Rumney wrote:
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 likeset alternate_editor=runemacs.exe -nwThe 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.
I do not think "emacs -nw" will work in all situations. I believe there should be a GUI version of emacsclient.exe. Does "emacs -nw" work if you use the GUI version?
Note: I added a GUI version to gnuclient.exe which I called gnuclientw.exe. The purpose of this was to avoid unnecessary console windows.
|[Prev in Thread]||Current Thread||[Next in Thread]|