DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=AUN5ty5NNJ8vvHd1S+ToDeVxJ4VJH
	iOTOuzenHQEJFUVVPl0jVg8XAaMNlb67f1TXAm3G4NDus+jEMGux3mWzlUj6Toz/
	vaqLu5XeSYKYfLgKgRq+SFnn1Vk4tvsn1sVS3L34QsGyDYMzaO/oP3vHpbNFhSHm
	+c4iS6fhLwJbnY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: Ugly Leper <ugly DOT leper AT gmail DOT com>
Date: Wed, 12 Jul 2017 07:16:48 +0100
Message-ID: <CAKqBF1gnbsiRURXOd7zo=w5hu9A_KMzchgoQMYCc_SeYDxjWvw@mail.gmail.com>
Subject: Starting from a Windows Command Prompt
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

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