From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: Patch to allow -nw to runemacs on w32
Date: Wed, 15 Nov 2006 21:05:27 +0100 [thread overview]
Message-ID: <455B7307.4030207@student.lu.se> (raw)
In-Reply-To: <uwt5whajh.fsf@gnu.org>
Eli Zaretskii wrote:
>> Date: Wed, 15 Nov 2006 14:44:25 +0100
>> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>>
>> In some situations you may want to be able to use the -nw option with
>> runemacs.exe.
>>
>
> What are those situations? We cannot judge the importance of applying
> this patch without knowing when the current behavior is an annoyance.
>
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
If my patch is applied of course. Otherwise the user just gets into the
trouble we discussed before (hidden emacs or a crashing emacs).
next prev parent reply other threads:[~2006-11-15 20:05 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 [this message]
2006-11-15 21:38 ` Jason Rumney
2006-11-15 22:02 ` Lennart Borgman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=455B7307.4030207@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).