unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Nicholas \"Indy\" Ray" <arelius@gmail.com>
To: 8268@debbugs.gnu.org
Subject: bug#8268: Windows Emacs Console persists while running running emacs.exe.
Date: Wed, 16 Mar 2011 20:42:56 -0700	[thread overview]
Message-ID: <AANLkTimkUTiS-yK4G0R+Jnh47NMEh=XGXx+iFwwFBC0m@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

This seems to be related to bug #1849, but perhaps never properly fixed.

Anyways, when opening emacs from Emacs.exe, which is difficult to not do in
Windows 7 with pinning to the task bar, Emacs will open with an unneeded
console window that cannot be destroyed.

This seems likely due to the fact that Emacs is spawned as a console
application when run in this manner.  However, I think there is a simple fix
that doesn't cause problems when the program is run as a console app.

By calling the FreeConsole win32 function when Emacs initializes it's GUI
this should kill any os spawned console windows, had they not been opened
separately.

See:
http://msdn.microsoft.com/en-us/library/ms683150%28v=vs.85%29.aspx

I've used this function to great effect in other applications, and am
confident it'd work. I'd have fixed it and created a patch myself, but I've
spent the last few hours trying to get Emacs to build on this weird setup I
have here.

Indy

[-- Attachment #2: Type: text/html, Size: 1224 bytes --]

             reply	other threads:[~2011-03-17  3:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17  3:42 Nicholas "Indy" Ray [this message]
2011-03-17  5:14 ` bug#8268: Windows Emacs Console persists while running running emacs.exe 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

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='AANLkTimkUTiS-yK4G0R+Jnh47NMEh=XGXx+iFwwFBC0m@mail.gmail.com' \
    --to=arelius@gmail.com \
    --cc=8268@debbugs.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).