From: Adam Dinwoodie <Adam.Dinwoodie@metaswitch.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: some kind of path problem when running bash script from windows shortcut
Date: Thu, 22 Mar 2012 18:40:00 -0000 [thread overview]
Message-ID: <CE9C056E12502146A72FD81290379E9A2C52D90F@ENFIRHMBX1.datcon.co.uk> (raw)
In-Reply-To: <4F6B6657.8050005@molconn.com>
LMH wrote:
> Thanks for the advice. I just ran cygcheck, but I'm supprised that you
> are asking folks to post that. The output contains some personal
> information, such as the computer name and user name, and I'm guessing
> that some folks would rather not post that.
You _did_ read the [problem reporting guidelines][0] before posting here,
right? Like the bits that say "include that file as *an attachment*"
(emphasis original) and "it is ok to redact sensitive information"?
[0]: http://cygwin.com/problems.html
> I added C:\cygwin\bin to the windows path. I guess I forgot environment
> variables when I did the re-install. One of these days I need to learn
> how to do post install config scripts so I don't have to spend two weeks
> getting my windows the way I want it.
So did it work? If it did, I don't really care about the cygcheck output
any more. If it didn't, I need to know that to be able to help.
Adam
--
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:[~2012-03-22 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 17:22 LMH
2012-03-22 17:37 ` Adam Dinwoodie
2012-03-22 17:50 ` LMH
2012-03-22 18:40 ` Adam Dinwoodie [this message]
2012-03-22 18:47 ` LMH
2012-03-23 14:05 ` Andrey Repin
2012-03-23 15:50 ` LMH
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=CE9C056E12502146A72FD81290379E9A2C52D90F@ENFIRHMBX1.datcon.co.uk \
--to=adam.dinwoodie@metaswitch.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).