public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Doug Henderson <djndnbvg@gmail.com>, cygwin@cygwin.com
Subject: Re: run.exe flashes non-hidden console window in cygwin64 on Win7Pro-64
Date: Thu, 23 Oct 2014 01:35:00 -0000	[thread overview]
Message-ID: <1606505198.20141023052833@yandex.ru> (raw)
In-Reply-To: <CAJ1FpuM=aDE0tAPb5Ez_TwW87j8ypBWp_RncETFaDQdNYLYYzA@mail.gmail.com>

Greetings, Doug Henderson!

>> Andrey, the flashing console flashes very quickly and I don't know how to slow it down.
>> It appears to have no title and no contents.

Normally, I just fire up a screen recorder in such cases. But I seems to have
missed the beginning of a discussion.

> run appears to work correctly when you use it at a cygwin shell prompt.

> run.exe is a cygwin executable; use ldd see the DLLs that it uses.

> Since your shortcut is not starting a windows GUI program, it starts a
> console window, possibly executing cmd.exe

Depends on the way shortcut is constructed... I don't think it ever touch
cmd.exe, there's no need to do so. But the console window is really the
run.exe itself. Most, if not all, of Cygwin applications are in fact "console
applications" in Windows terms.

> Have you tried changing the shortcut to cause it to open the window
> minimized? I vaguely remember doing something like that with the
> cygwin.bat clone I used to start a (non-X windows) rxvt window.

That may at least alleviate the window flashing in the face of a user.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 23.10.2014, <5:25>

Sorry for my terrible english...


--
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:[~2014-10-23  1:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 19:43 Starting mintty via run.exe John Wiersba
2014-10-16 23:34 ` Eliot Moss
2014-10-17  3:39   ` John Wiersba
2014-10-17  3:51     ` John Wiersba
2014-10-17 13:14       ` Eliot Moss
2014-10-17 21:52         ` cygcheck -s segfaults in cygwin64 on Win7Pro-64 John Wiersba
2014-10-18  3:59           ` Marco Atzeri
2014-10-20 22:39             ` John Wiersba
2014-10-21  8:03               ` Andrew Schulman
2014-10-21 11:03                 ` Corinna Vinschen
2014-10-21 15:31                   ` John Wiersba
2014-10-21 16:54         ` run.exe flashes non-hidden console window " John Wiersba
2014-10-22 13:50           ` Andrey Repin
2014-10-22 20:37             ` John Wiersba
2014-10-23  0:20               ` Doug Henderson
2014-10-23  1:35                 ` Andrey Repin [this message]
2014-10-23  8:42                   ` Andrew Schulman
     [not found]                   ` <1414037878.2285.YahooMailNeo@web162805.mail.bf1.yahoo.com>
2014-10-23 12:24                     ` John Wiersba
2014-10-23 17:56                       ` Achim Gratz
2014-10-23 18:47                         ` John Wiersba
2014-10-23 18:34                       ` Doug Henderson
2014-10-23 19:15                         ` John Wiersba
2014-10-23 19:40           ` Doug Henderson
2014-10-23 20:26             ` John Wiersba
2014-10-23 20:52               ` Achim Gratz
2014-10-23 21:25                 ` John Wiersba

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=1606505198.20141023052833@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=djndnbvg@gmail.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).