public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Is it possible to hide emacs-w32 console window?
Date: Sun, 29 May 2016 17:25:00 -0000	[thread overview]
Message-ID: <75fd4118-49a9-e999-1c7d-6b1ace782fc6@cornell.edu> (raw)
In-Reply-To: <87d1o52fx2.fsf@gavenkoa.example.com>

On 5/29/2016 8:43 AM, Oleksandr Gavenko wrote:
> 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.

You can avoid the console window by using Cygwin's run.exe.  See the 
shortcut for the X server for an example of this.  (You do get a brief 
console window, but it immediately disappears.)

> I don't know if it is possible to link emacs-w32 with --subsystem=windows.

I don't either, and I'm not interested in experimenting with this 
without knowing what all the consequences would be.

Ken


--
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

  reply	other threads:[~2016-05-29 13:59 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
2016-05-29 17:25     ` Ken Brown [this message]
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=75fd4118-49a9-e999-1c7d-6b1ace782fc6@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).