From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Is it possible to hide emacs-w32 console window?
Date: Sun, 29 May 2016 14:05:00 -0000 [thread overview]
Message-ID: <87d1o52fx2.fsf@gavenkoa.example.com> (raw)
In-Reply-To: <463b9a2b-cad4-5fe7-f175-1a723c0bcf63@cornell.edu>
On 2016-05-29, Ken Brown wrote:
> On 5/28/2016 5:08 PM, Oleksandr Gavenko wrote:
>> emacs-w32 starts console window and that useless window disturbs during task
>> switching (by Alt+TAB) and take space on TaskBar.
>>
>> Is it possible to hide emacs-w32 console window?
>
> Sorry, I don't know what console window you're talking about. Exactly how do
> you start emacs-w32? I start it by typing 'emacs-w32 &' in a Cygwin terminal
> (mintty), and there's no console window.
>
Sorry I forgot to add this detail.
I use Win+R emacs-w32 ENTER.
If I start from terminal (cmd.exe or mintty) it works as in your case.
But otherwise "ConsoleWindowClass" (from spy++) window is opened (like cmd.exe
but without working prompt) along with regular Emacs windows.
Closing that window also closes Emacs.
I try:
#include <windows.h>
int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, PSTR lpCmdLine, INT nCmdShow) {
MessageBoxW(NULL, L"Hello", L"Ok", MB_OK);
return 0;
}
with:
gcc -Wl,--subsystem,windows -o mb.exe mb.c
and on:
Win+R C:\home\my\tmp\mb.exe ENTER
I don't see console window.
I don't know if it is possible to link emacs-w32 with --subsystem=windows.
mintty.exe has dependency on cygwin1.dll and does not bring up cmd-like
console along with xterm console.
--
http://defun.work/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-29 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 23:35 Oleksandr Gavenko
2016-05-29 3:08 ` Ken Brown
2016-05-29 14:05 ` Oleksandr Gavenko [this message]
2016-05-29 17:25 ` Ken Brown
2016-05-30 10:40 ` Oleksandr Gavenko
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=87d1o52fx2.fsf@gavenkoa.example.com \
--to=gavenkoa@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).