From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: git 2.8.3 spurious output
Date: Thu, 09 Jun 2016 19:37:00 -0000 [thread overview]
Message-ID: <C2079F30-ECD8-4BED-A63B-5B5F482FFC53@etr-usa.com> (raw)
In-Reply-To: <087DA9770269374FB58D517AC05CCA3F017497826F@mbx04.nvlsi.no>
On Jun 9, 2016, at 1:52 AM, Cufi, Carles <Carles.Cufi@nordicsemi.no> wrote:
>
>> I prefer to use Cygwin most of the
>> time, then run a âmingwâ script I wrote to temporarily shift my Cygwin
>> environment to MinGW mode:
>
> This sounds like a very good idea, but the problem is that sometimes I need to run mingw commands from standard Windows Command Prompts.
So write a mingw.bat file that does something similar for cmd.exe.
It won’t be seen from Cygwin even if it’s in Cygwin’s path because Cygwin won’t run it without the “.bat” extension, and Cygwin’s mingw shell script won’t be run by cmd.exe, so the “mingw” command will mean something completely different to each shell.
Incidentally, I see that I forgot to fix a /c -> /cygdrive/c in the script I posted. (I normally run with cygdrive mounted at the root, and write my scripts accordingly.)
--
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 prev parent reply other threads:[~2016-06-09 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 7:52 Cufi, Carles
2016-06-09 19:37 ` Warren Young [this message]
2016-06-11 19:20 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2016-06-08 14:41 Cufi, Carles
2016-06-08 16:45 ` Achim Gratz
2016-06-08 14:19 Cufi, Carles
2016-06-08 14:27 ` Ken Brown
2016-06-08 14:33 ` Warren Young
2016-06-08 13:57 Cufi, Carles
2016-06-08 14:06 ` Ken Brown
2016-06-08 9:35 Cufi, Carles
2016-06-08 13:45 ` Ken Brown
2016-06-08 13:56 ` Ken Brown
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=C2079F30-ECD8-4BED-A63B-5B5F482FFC53@etr-usa.com \
--to=wyml@etr-usa.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).