GNU bug report logs - #13850
Emacs for Windows: Launch better from a command prompt

Previous Next

Package: emacs;

Reported by: Andrew Pennebaker <andrew.pennebaker <at> gmail.com>

Date: Fri, 1 Mar 2013 20:55:01 UTC

Severity: wishlist

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #26 received at 13850 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 13850 <at> debbugs.gnu.org, help-emacs-windows <at> gnu.org,
 Andrew Pennebaker <andrew.pennebaker <at> gmail.com>
Subject: Re: bug#13850: Emacs for Windows: Launch better from a command prompt
Date: Sun, 01 May 2022 11:12:36 +0200
Eli Zaretskii <eliz <at> 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




This bug report was last modified 3 years and 78 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.