public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Is it possible to hide emacs-w32 console window?
Date: Mon, 30 May 2016 10:40:00 -0000	[thread overview]
Message-ID: <87zir72a43.fsf@gavenkoa.example.com> (raw)
In-Reply-To: <75fd4118-49a9-e999-1c7d-6b1ace782fc6@cornell.edu>

On 2016-05-29, Ken Brown wrote:

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

Thanks, that helped.

I tested with "Win+R run emacs-w32 ENTER" but better to have wrapper to
simplify typing.

run(1) man page explains some details:

  NAME
       run - start programs with hidden console window

  DESCRIPTION

       Windows programs are either GUI programs or console programs. When
       started console programs will either attach to an existing console or
       create a new one. GUI programs can never attach to an exiting console.
       There is no way to attach to an existing console but hide it if started
       as GUI program.

       run will do this for you. It works as intermediate and starts a program
       but makes the console window hidden.

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

      reply	other threads:[~2016-05-30  9:01 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
2016-05-30 10:40       ` Oleksandr Gavenko [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=87zir72a43.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).