From: Ron Parker <ron.parker@mobot.org>
Date: Tue, 24 Apr 2007 13:34:22 GMT
Subject: RE: [OT] CDPATH
Message-ID: <769697AE3E25EF4FBC0763CD91AB1B0201D496D1@MBGMail01.mobot.org>
In-Reply-To: <Pine.LNX.4.64.0704232351530.8430@beast.quantumfyre.co.uk>

Junio C Hamano <junkio@cox.net> wrote:

> Are you sure bash-completion is the culprit, not your CDPATH?

Sorry, I was half-asleep yesterday.  Of course it was CDPATH and not 
bash-completion.

Julian Phillips <julian@quantumfyre.co.uk> wrote:

> CDPATH is Ok as long as it stays as an interactive shell
> variable.

Based on a shell I used years ago that had built-in functionality similar to
CDPATH, I naïvely *assumed* CDPATH would only impact interactive shells.

In another message, Julian wrote:

> I guess part of the problem is that a lot of these people don't actually 
> understand the difference between shell variables and environment 
> variables, or why the distinction is useful.  Plenty of people seem to do 
> "export FOO=..." by rote.

Not quite my case, but assumptions are dangerous things.  Based on my 
assumption, I intentionally exported CDPATH so it would propagate when
I "xterm&".  Grr, I guess I'll have to alias xterm instead.

Thanks for the enlightenment gentlemen.

Yet another reason I like "git reset --hard HEAD" for stupid patch removal.

Now if there was a "reset --hard HEAD" function for some people I've met...

Thanks,

Ron