From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13850@debbugs.gnu.org, help-emacs-windows@gnu.org
Subject: bug#13850: Emacs for Windows: Launch better from a command prompt
Date: Sun, 01 May 2022 11:12:36 +0200 [thread overview]
Message-ID: <87v8upr4zf.fsf@gnus.org> (raw)
In-Reply-To: <83k3pquuqy.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 02 Mar 2013 09:27:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> We already do: just invoke runemacs.exe rather than emacs.exe.
>
> As for forking a thread: it is a bit more complex than that. (We
> already start at least 2 threads at startup.) The 2 most important
> problems are (1) the same executable should be able to run in a text
> terminal session under -nw, and (2) we don't want the GUI session to
> have a console. runemacs.exe solves both.
>
> Any reasons not to close this bug?
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
"Use runemacs" seems like it's the correct answer here, so I'm closing
this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-01 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 20:49 bug#13850: Emacs for Windows: Launch better from a command prompt Andrew Pennebaker
2013-03-01 22:54 ` K. Frank
2013-03-02 7:27 ` bug#13850: " Eli Zaretskii
[not found] ` <83k3pquuqy.fsf@gnu.org>
[not found] ` <CAHXt_SXakTei9TZFvjEmuggaGNHCQMq4xYfJ0Qtq1NwvOy_82g@mail.gmail.com>
2013-03-02 14:59 ` Eli Zaretskii
[not found] ` <CAHXt_SV+VVnj2yw189cNq15sKNqMonWZm2zH_FN3nOS5_PSa3w@mail.gmail.com>
2013-03-02 15:33 ` Eli Zaretskii
[not found] ` <CAHXt_SUFhkL64WPzOqTKq0Qq6FYFafC_t4m04qUnreB1Fd2MsQ@mail.gmail.com>
2013-03-02 16:22 ` Eli Zaretskii
2013-03-02 16:25 ` Lennart Borgman
2022-05-01 9:12 ` Lars Ingebrigtsen [this message]
2022-05-01 9:57 ` Joel Reicher
[not found] ` <86zgk1lgm8.fsf@gmail.com>
2022-05-01 10:09 ` Eli Zaretskii
[not found] ` <83bkwh7eec.fsf@gnu.org>
2022-05-01 10:35 ` Joel Reicher
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=87v8upr4zf.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13850@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=help-emacs-windows@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).