This is the mail archive of the
mailing list for the Cygwin project.
Re: Starting from a Windows Command Prompt
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Jul 2017 17:25:46 -0600
- Subject: Re: Starting from a Windows Command Prompt
- Authentication-results: sourceware.org; auth=none
- References: <CAKqBF1gnbsiRURXOd7zo=w5hu9A_KMzchgoQMYCc_SeYDxjWvw@mail.gmail.com> <1cc1103d-708a-868d-c513-cc0dac4656e6@SystematicSw.ab.ca> <email@example.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
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
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple