From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#8268: Windows Emacs Console persists while running running emacs.exe. Date: Sat, 18 Feb 2017 12:27:21 +0200 Message-ID: <83d1efrdyu.fsf@gnu.org> References: <2333196f-e9be-4e1a-aa28-2351e1396a3d@r4g2000prm.googlegroups.com> <87r334kr9q.fsf@users.sourceforge.net> <87lgtblcxr.fsf@users.sourceforge.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1487413635 32649 195.159.176.226 (18 Feb 2017 10:27:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 18 Feb 2017 10:27:15 +0000 (UTC) Cc: lekktu@gmail.com, camel322@gmail.com, 8268@debbugs.gnu.org To: npostavs@users.sourceforge.net Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 18 11:27:11 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cf2EM-0007dE-4R for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Feb 2017 11:27:06 +0100 Original-Received: from localhost ([::1]:57923 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cf2ER-0003lC-VO for geb-bug-gnu-emacs@m.gmane.org; Sat, 18 Feb 2017 05:27:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cf2EL-0003kw-4F for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2017 05:27:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cf2EI-0000Aj-JM for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2017 05:27:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:45978) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cf2EI-0000Af-FU for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2017 05:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cf2EI-00055V-7R for bug-gnu-emacs@gnu.org; Sat, 18 Feb 2017 05:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 Feb 2017 10:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 8268 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 8268-submit@debbugs.gnu.org id=B8268.148741362119550 (code B ref 8268); Sat, 18 Feb 2017 10:27:02 +0000 Original-Received: (at 8268) by debbugs.gnu.org; 18 Feb 2017 10:27:01 +0000 Original-Received: from localhost ([127.0.0.1]:44177 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cf2EH-00055G-5F for submit@debbugs.gnu.org; Sat, 18 Feb 2017 05:27:01 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:39557) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cf2EG-000553-5g for 8268@debbugs.gnu.org; Sat, 18 Feb 2017 05:27:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cf2E7-0008WP-VE for 8268@debbugs.gnu.org; Sat, 18 Feb 2017 05:26:55 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44156) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cf2E7-0008WL-RJ; Sat, 18 Feb 2017 05:26:51 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:1150 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cf2E6-000307-W0; Sat, 18 Feb 2017 05:26:51 -0500 In-reply-to: <87lgtblcxr.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:129488 Archived-At: > From: npostavs@users.sourceforge.net > Date: Sun, 12 Feb 2017 09:08:00 -0500 > Cc: oCameLo , 8268@debbugs.gnu.org > > Juanma Barranquero writes: > > > On Sun, Feb 12, 2017 at 4:43 AM, wrote: > > > >> Something like this? > >> > >> --- i/nt/README.W32 > >> +++ w/nt/README.W32 > >> @@ -94,6 +94,12 @@ See the end of the file for license conditions. > >> (non-windowed) mode of operation is most useful if you have a telnet > >> server on your machine, allowing you to run Emacs remotely. > >> > >> +* Pinning Emacs to the taskbar (Windows 7 and higher) > >> + > >> + After starting Emacs the first time, pin it to the taskbar, then > >> + edit the properties (via shift-right-click) so that the executable > >> + path to points to runemacs.exe instead of emacs.exe. > >> + > >> * EXE files included > >> > >> Emacs comes with the following executable files in the bin directory. > > > > Yes, though the emacs-25 branch already has something like that in nt/README.W32 > > > > + runemacs.exe - A wrapper for running Emacs as a GUI application > > without popping up a command prompt window. If you create a > > desktop shortcut for invoking Emacs, make it point to this > > executable, not to emacs.exe. > > > > It's talking about a desktop shortcut and not the taskbar, but it is > > the same idea. Perhaps change it to "If you create a desktop shortcut > > for invoking Emacs, or pin Emacs to the taskbar, modify the shortcut > > so it points to this executable, not to emacs.exe". Or something like > > that. > > If I understand correctly an important difference is that for the > shortcut, you can just create a shortcut to runemacs.exe directly. > Whereas for the taskbar, you have to start emacs first, and only then > modify the path. That's a bit unintuitive and seems worth calling out > in its own paragraph. I did a merge of the two ideas, and pushed the result to the emacs-25 branch. Thanks.