public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Subject: Re: Help Understanding Path Issue
Date: Fri, 30 Jun 2006 16:25:00 -0000	[thread overview]
Message-ID: <e83j15$r2g$2@sea.gmane.org> (raw)
In-Reply-To: <Pine.GSO.4.63.0606291853340.590@access1.cims.nyu.edu>

Igor Peshansky wrote:
> On Thu, 29 Jun 2006, mwoehlke wrote:
>> While CC'ing me for some reason(?), Igor Peshansky wrote:
>> (And was there a reason for that, or did you just hit 'reply all' by
>> accident/reflex/because the hippo made me?)
> 
> I always hit "Reply-All", and you didn't have Reply-To: set.

Ah, so I don't. Probably because I am also using gmane to look at KDE 
lists; setting reply-to <cygwin> would be a little strange in that case. 
Too bad TB doesn't let you set things per-group :-(.

Anyway, thanks for the clarification; no worries.

>>> Actually, the list of variables automatically translated by Cygwin was
>>> posted here at some point (it may even be in the FAQ).  At the very
>>> least it's PATH, HOME, and LD_LIBRARY_PATH, but there may be others.
>> 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...

Ok, I won't... but at least my confusion is shared. I feel better now. :-)

-- 
Matthew
Do not expose to hippos. Doing so may void your warranty.

  parent reply	other threads:[~2006-06-30 16:25 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
2006-06-30 16:25         ` mwoehlke [this message]
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='e83j15$r2g$2@sea.gmane.org' \
    --to=mwoehlke@tibco.com \
    --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).