https://bugzilla.novell.com/show_bug.cgi?id=402597
User geoff@cs.hmc.edu added comment
https://bugzilla.novell.com/show_bug.cgi?id=402597#c16
--- Comment #16 from Geoff Kuenning 2008-08-15 16:41:15 MDT ---
Bash's bug-reporting system is a script named "bashbug", which sends mail to
their list. I suppose they have an online tracker but I don't know where it
is.
They've responded (by e-mail) to my reports. The first response says, in
essence, "That's the way the POSIX standard says CDPATH should behave." The
second says, in essence, "all variables are documented and it's the
script-writers problem to deal with it." He also pointed out that modifying
bash to start unsetting dangerous variables is risky from a
backwards-compatibility standpoint (which I think is a fair point). Finally,
he mentioned that the CDPATH issue has been reported multiple times. I'd take
that letter comment as a sign of a big design error, but that's going to be a
hard sell.
I'm going to reply, pointing out that the POSIX standard is (a) ambiguous about
whether CDPATH needs to be reported for non-interactive shells, and (b) wrong
for asking it to be reported to stdout. But I doubt I'll win the argument.
So I think we're stuck with it. Something I came across pointed out that you
can always write "cd ./foo" instead of "cd foo", but that's hardly more
convenient that simply unsetting CDPATH.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.