From: Lennart Borgman <lennart.borgman.073@student.lu.se>
Cc: Emacs Devel <emacs-devel@gnu.org>, Jason Rumney <jasonr@gnu.org>
Subject: Re: Patch to allow -nw to runemacs on w32
Date: Wed, 15 Nov 2006 17:12:28 +0100 [thread overview]
Message-ID: <455B3C6C.9020206@student.lu.se> (raw)
In-Reply-To: <f7ccd24b0611150747l75f21d50ma40bf6fb5a37a8a3@mail.gmail.com>
Juanma Barranquero wrote:
> On 11/15/06, Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:
>
>> I get a fatal error, not just a hidden window.
>
> I get the same result that Jason: no error of any kind, just Emacs
> runs hidden.
You are right. I also just get a hidden emacs.exe if I add -Q. Though I
would not say a sometimes hidden, sometimes crashing emacs is very good ;-)
And at a second thought it seems natural that runemacs creates a new
window - even if it is a console window. That is what runemacs is for,
isn't it?
>
> BTW, the same happens with your patch if -nw is not the first
> argument, for example:
>
> runemacs -xrm "Emacs.Background:red" -nw
That is by intent. I handle this argument like the other arguments that
are handled in runemacs. Or, it is much easier doing it that way.
next prev parent reply other threads:[~2006-11-15 16:12 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 [this message]
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
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=455B3C6C.9020206@student.lu.se \
--to=lennart.borgman.073@student.lu.se \
--cc=emacs-devel@gnu.org \
--cc=jasonr@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.