Re: [PATCH v2 5/8] builtins/source: parse the -i option
From:
Chet Ramey
Subject:
Re: [PATCH v2 5/8] builtins/source: parse the -i option
Date:
Thu, 16 May 2024 11:36:50 -0400
User-agent:
Mozilla Thunderbird
On 5/15/24 6:27 PM, Robert Elz wrote:
All I suggested
was having a BASH_SOURCE_PATH set to the empty string mean that no path
lookup should be done,
You can already do this; there's no reason to add these semantics to a
variable setting.
and any attempt to use a relative path (and you
can exclude ./anything or ../anything from that if you prefer - ie:
Those are not relative paths.
exclude anything which would skip the PATH-like search anyway) would
simply fail (not just return itself and be attempted relative to ".")
Is this really valuable?
| So let's move the state of the art forward.
That isn't going to happen if you make the path searched have a BASH_*
variable name.
Maybe. We'll have to see. People will object no matter what the name is.
I have high hopes for `GLOBSORT', though.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/