From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Starting from a Windows Command Prompt
Date: Wed, 12 Jul 2017 23:25:00 -0000 [thread overview]
Message-ID: <4b21d6ac-25c8-9f6e-9af7-f2420774120d@SystematicSw.ab.ca> (raw)
In-Reply-To: <49340806.20170712231509@yandex.ru>
On 2017-07-12 14:15, Andrey Repin wrote:
> Brian Inglis wrote:
>> On 2017-07-12 00:16, Ugly Leper wrote:
>>> Starting from a Windows Command Prompt, and using a syntax recommended
>>> from years ago I still start a bash shell with
>>> start /wait bin\bash (i.e. not just bin\bash)
>>> and a mintty shell with
>>> start bin\mintty (i.e. not just bin\mintty)
>>> and yet experiment shows that both simplified forms in brackets "work".
>>> Am I gaining / losing anything by sticking with the older longer
>>> syntax, or can I just dive in, as in brackets?
>
>> Running with start, like cygstart, spawns a separate window process
>
> Not necessarily.
> Ref: START /B
Only in that case does it start a background console process sharing the cmd
window for output, like Unix shell jobs, but the program apparently goes
squirrelly if it tries to do any console input, although msg and dialogue boxes
work.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
prev parent reply other threads:[~2017-07-12 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:16 Ugly Leper
2017-07-12 10:20 ` Andrey Repin
2017-07-12 18:28 ` Brian Inglis
2017-07-12 20:20 ` Andrey Repin
2017-07-12 23:25 ` Brian Inglis [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=4b21d6ac-25c8-9f6e-9af7-f2420774120d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).