From: Juanma Barranquero <lekktu@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 38367@debbugs.gnu.org
Subject: bug#38367: 26.3; Cannot start Emacs with -nw option, starting with Emacs 26.1
Date: Tue, 26 Nov 2019 03:45:05 +0100 [thread overview]
Message-ID: <CAAeL0SQKVX9_PUhg6QTyeAz-dzV1f78Q-Yw8-LFW7Tu+ciOENw@mail.gmail.com> (raw)
In-Reply-To: <f2ceb108-2de4-4714-9208-b98073485d8c@default>
[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]
On Tue, Nov 26, 2019 at 1:56 AM Drew Adams <drew.adams@oracle.com> wrote:
> 24.5 works fine for me with -nw.
Do you mean that if you create a desktop shortcut to 24.5's runemacs.exe
that runs it with -Q -nw, and click on it, you get Emacs running in a
console?
Because I get an Emacs running with a hidden console (no visible frame).
> That's what I've used for -nw in the past.
> But I just tried plain `emacs' for -nw, and
> that works too. (I use plain `emacs' for GUI.)
I'm confused now.
What do you mean with "That's what I've used for -nw in the past"? From a
shortcut, or from CMD?
> Does Emacs 26 on Windows 10 work for you
> with -nw?
26.3 works as expected:
1) "emacs.exe -Q -nw" from CMD: starts a console Emacs inside CMD
2) "emacs.exe -Q" from CMD: starts a windows Emacs, but it's attached to
the original CMD.
3) "runemacs.exe -Q -nw" from CMD: starts a detached console Emacs (i.e., I
see nothing because there's no window)
4) "runemacs.exe -Q" from CMD: starts a detached windows Emacs (CMD is
available to use).
5) "emacs.exe -Q -nw" from a shortcut: stars a console Emacs.
6) "emacs.exe -Q" from a shortcut: Stars a windows Emacs, but there's a
visible console.
7) "runemacs.exe -Q -nw" from a shortcut: starts a console Emacs, but the
console is hidden, so nothing is visible.
8) "runemacs.exe -Q" from a shortcut: starts a windows Emacs.
Basically, runemacs.exe exists *specifically* to help with 2) and 6),
because windows Emacs *always* creates a console, but when you're running a
windows Emacs, you don't want to see it (it's just a nuisance).
But if you're trying to run a console Emacs, "emacs.exe -Q -nw" is what you
want, either in a shortcut or from the command line.
So, what you see is not a bug, and I think it's always been so. I just
tried with 20.7.3 and I get the very same behavior.
[-- Attachment #2: Type: text/html, Size: 2489 bytes --]
next prev parent reply other threads:[~2019-11-26 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 2:21 bug#38367: 26.3; Cannot start Emacs with -nw option, starting with Emacs 26.1 Drew Adams
2019-11-25 22:48 ` Juanma Barranquero
2019-11-26 0:55 ` Drew Adams
2019-11-26 2:45 ` Juanma Barranquero [this message]
2019-11-26 6:15 ` Drew Adams
2019-11-26 9:33 ` martin rudalics
2019-11-26 13:12 ` Juanma Barranquero
2019-12-07 18:22 ` Tomas Nordin
2019-12-08 3:35 ` 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=CAAeL0SQKVX9_PUhg6QTyeAz-dzV1f78Q-Yw8-LFW7Tu+ciOENw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=38367@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.