From: Ugly Leper <ugly.leper@gmail.com>
To: cygwin@cygwin.com
Subject: Starting from a Windows Command Prompt
Date: Wed, 12 Jul 2017 06:16:00 -0000 [thread overview]
Message-ID: <CAKqBF1gnbsiRURXOd7zo=w5hu9A_KMzchgoQMYCc_SeYDxjWvw@mail.gmail.com> (raw)
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?
Thank you!
--
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
next reply other threads:[~2017-07-12 6:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 6:16 Ugly Leper [this message]
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
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='CAKqBF1gnbsiRURXOd7zo=w5hu9A_KMzchgoQMYCc_SeYDxjWvw@mail.gmail.com' \
--to=ugly.leper@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).