From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Patch to allow -nw to runemacs on w32
Date: Wed, 15 Nov 2006 23:02:33 +0100 [thread overview]
Message-ID: <455B8E79.5060105@student.lu.se> (raw)
In-Reply-To: <455B88CA.4060703@gnu.org>
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 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.
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.
next prev parent reply other threads:[~2006-11-15 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 13:44 Patch to allow -nw to runemacs on w32 Lennart Borgman
2006-11-15 15:22 ` Jason Rumney
2006-11-15 15:34 ` Lennart Borgman
2006-11-15 15:47 ` Juanma Barranquero
2006-11-15 15:55 ` Juanma Barranquero
2006-11-15 16:12 ` Lennart Borgman
2006-11-15 16:37 ` Juanma Barranquero
2006-11-15 18:57 ` Juanma Barranquero
2006-11-15 21:35 ` Jason Rumney
2006-11-15 21:20 ` Lennart Borgman
2006-11-15 21:29 ` Juanma Barranquero
2006-11-15 17:41 ` Eli Zaretskii
2006-11-15 20:05 ` Lennart Borgman
2006-11-15 21:38 ` Jason Rumney
2006-11-15 22:02 ` Lennart Borgman [this message]
2006-11-16 4:40 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=455B8E79.5060105@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.