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 12:28:54 -0600
- Subject: Re: Starting from a Windows Command Prompt
- Authentication-results: sourceware.org; auth=none
- References: <CAKqBF1gnbsiRURXOd7zo=w5hu9A_KMzchgoQMYCc_SeYDxjWvw@mail.gmail.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
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 for the
program, as does running mintty with or without start or cygstart.
The difference with bash and start /wait is you currently keep a cmd shell
window hanging around rather than running bash as a subshell in your cmd window.
Why not take advantage of Windows, and pin Cygwin shortcuts to your Start Menu
and/or Taskbar, so you can more easily start mintty or bash in their own windows
with just a click, almost like a real Unix X Window environment? ;^>
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple