On 5/14/24 5:40 PM, Robert Elz wrote:
Date: Tue, 14 May 2024 15:51:10 -0400
From: Chet Ramey <chet.ra...@case.edu>
Message-ID: <c88fb0b0-4fd8-437d-bc8f-ab7f5335b...@case.edu>
| What do folks think about forcing an option to enable using
| BASH_SOURCE_PATH? Should it be required? Is it necessary? (I personally
| think it is not.) We discussed this briefly last week but without any
| conclusion.
I'd make it set to '' mean that only paths containing
a '/' would work for the '.' command) and:
Why make it different from other PATH-like variables, where a null
component is equivalent to "."?
I agree, but it should be expected to be defined in a profile type file
if it needs to be defined at all (a system wide one, or a user's personal one).
The default (as compiled without extra config) should be unset.
That's the idea.
But I don't think any of this is needed at all. I agree with the OP
that having '.' use PATH is archaic, and fairly dumb.
So let's move the state of the art forward.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
