From: One Angry User <angry@lusers.org>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: Help Understanding Path Issue
Date: Fri, 30 Jun 2006 16:10:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.63.0606301208560.22269@access1.cims.nyu.edu> (raw)
In-Reply-To: <20060630095733.GR18873@calimero.vinschen.de>
On a sunny Friday morning, the 30th day of June, 2006, Corinna Vinschen's computer deigned to emit the following stream of bytes:
> On Jun 29 18:57, Igor Peshansky wrote:
> > On Thu, 29 Jun 2006, mwoehlke wrote:
> > > LD_LIBRARY_PATH? Since when does Windows have any clue what to do with
> > > *that*? (Or it it folded into PATH?)
> >
> > Hmm... [Digs into the sources]... Yep, here's the full list as of today:
> > PATH, HOME, LD_LIBRARY_PATH (yes!), TMPDIR, TMP, TEMP. And no,
> > LD_LIBRARY_PATH is not folded into PATH. And don't ask me why it gets
> > converted...
>
> A quick grep over the ChangeLogs is sometimes very helpful.
Quick grep? What's that? I only have GNU grep installed on my machine.
Is Quick grep something I should try to compile from source myself? Does
it do a better job than GNU grep? Is it compatible? What are the options
I should use?
OAU
next prev parent reply other threads:[~2006-06-30 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <006a01c69b13$658a1570$3201a8c0@Purcell9100>
[not found] ` <e7vd4o$js1$1@sea.gmane.org>
[not found] ` <Pine.GSO.4.63.0606291828560.590@access1.cims.nyu.edu>
2006-06-29 22:49 ` mwoehlke
2006-06-29 22:57 ` Igor Peshansky
2006-06-30 9:57 ` Corinna Vinschen
2006-06-30 10:16 ` Dave Korn
2006-06-30 11:03 ` Corinna Vinschen
2006-06-30 11:10 ` Dave Korn
2006-06-30 12:27 ` Corinna Vinschen
2006-06-30 15:58 ` Eric Blake
2006-06-30 16:19 ` Igor Peshansky
2006-06-30 16:17 ` Igor Peshansky
2006-06-30 16:15 ` Igor Peshansky
2006-06-30 16:11 ` Igor Peshansky
2006-06-30 16:10 ` One Angry User [this message]
2006-06-30 16:25 ` mwoehlke
2006-06-30 16:29 ` Igor Peshansky
2006-06-30 21:32 ` mwoehlke
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=Pine.GSO.4.63.0606301208560.22269@access1.cims.nyu.edu \
--to=angry@lusers.org \
--cc=cygwin-talk@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).