all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: lekktu@gmail.com, camel322@gmail.com, 8268@debbugs.gnu.org
Subject: bug#8268: Windows Emacs Console persists while running running emacs.exe.
Date: Sat, 18 Feb 2017 12:27:21 +0200	[thread overview]
Message-ID: <83d1efrdyu.fsf@gnu.org> (raw)
In-Reply-To: <87lgtblcxr.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)

> From: npostavs@users.sourceforge.net
> Date: Sun, 12 Feb 2017 09:08:00 -0500
> Cc: oCameLo <camel322@gmail.com>, 8268@debbugs.gnu.org
> 
> Juanma Barranquero <lekktu@gmail.com> writes:
> 
> > On Sun, Feb 12, 2017 at 4:43 AM, <npostavs@users.sourceforge.net> 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.





      reply	other threads:[~2017-02-18 10:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17  3:42 bug#8268: Windows Emacs Console persists while running running emacs.exe Nicholas "Indy" Ray
2011-03-17  5:14 ` Juanma Barranquero
2011-03-17  5:19   ` Nicholas "Indy" Ray
2011-03-17  6:31     ` Jason Rumney
2011-03-17  7:19       ` Jan D.
2011-03-17 12:26         ` Juanma Barranquero
2011-03-17 19:30       ` Juanma Barranquero
2011-03-17  5:39 ` Eli Zaretskii
2011-03-17  5:42   ` Nicholas "Indy" Ray
2011-03-17 12:48     ` Juanma Barranquero
2011-03-17 16:29       ` Nicholas "Indy" Ray
2011-03-17 18:19         ` Juanma Barranquero
2011-03-17 18:25           ` Nicholas "Indy" Ray
2011-03-17 19:27             ` Juanma Barranquero
2011-03-18  3:53               ` Nicholas "Indy" Ray
2011-03-18  6:43                 ` Juanma Barranquero
2011-03-18  8:08                 ` Eli Zaretskii
2011-03-23 21:50                   ` Nicholas "Indy" Ray
2011-03-24  4:07                     ` Eli Zaretskii
     [not found]             ` <mailman.14.1300390628.11234.bug-gnu-emacs@gnu.org>
2011-04-03 10:46               ` oCameLo
2011-04-03 12:18                 ` Juanma Barranquero
2017-02-12  3:43                   ` npostavs
2017-02-12 12:47                     ` Juanma Barranquero
2017-02-12 14:08                       ` npostavs
2017-02-18 10:27                         ` Eli Zaretskii [this message]

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=83d1efrdyu.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=8268@debbugs.gnu.org \
    --cc=camel322@gmail.com \
    --cc=lekktu@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /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.