From: Drew Adams <drew.adams@oracle.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 38367@debbugs.gnu.org
Subject: bug#38367: 26.3; Cannot start Emacs with -nw option, starting with Emacs 26.1
Date: Mon, 25 Nov 2019 22:15:20 -0800 (PST) [thread overview]
Message-ID: <1e515a8a-0112-4b3c-81b8-6a40b7a9835e@default> (raw)
In-Reply-To: <CAAeL0SQKVX9_PUhg6QTyeAz-dzV1f78Q-Yw8-LFW7Tu+ciOENw@mail.gmail.com>
>> 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?
That's what I meant. But I had it backward
(`emacs' vs `runemacs'). Sorry for the noise -
I'll close the bug.
The Target on the Shortcut tab is this:
y:\Emacs-24.5\bin\emacs.exe -nw
^^^^^
That works fine for me in all Emacs versions,
including 24.5 and 26.x.
I don't actually use -nw, except rarely, for
testing something. For 26.x I tried to do
what I've done before for -nw, but I got it
backward.
> What do you mean with "That's what I've used for -nw in the past"? From a shortcut, or from CMD?
I always use shortcuts, not CMD.
What I meant and wrote was backward from what I
actually do (which works, including in Emacs 26).
I use `runemacs', not `emacs', for GUI, and
I use `emacs', not `runemacs', for -nw.
What I said was mistakenly the opposite of that.
Thanks.
next prev parent reply other threads:[~2019-11-26 6:15 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
2019-11-26 6:15 ` Drew Adams [this message]
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=1e515a8a-0112-4b3c-81b8-6a40b7a9835e@default \
--to=drew.adams@oracle.com \
--cc=38367@debbugs.gnu.org \
--cc=lekktu@gmail.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.