On 03/02/2012 02:50 AM, Chet Ramey wrote: > On 2/29/12 2:42 PM, Eric Blake wrote: > > In the middle of the histrionics and gibberish, we have the nugget of an > actual proposal (thanks, Eric): > > [to allow `.' to look anchored relative pathnames up in $PATH] > >> About the best we can do is accept a patch (are you willing to write it? >> if not, quit complaining) that would add a new shopt, off by default, to >> allow your desired alternate behavior. > > Maybe we can have a rational discussion about that. > Or here is a what it sounds as a marginally better idea to me: Bash could start supporting a new environment variable like "BASHLIB" (a' la' PERL5LIB) or "BASHPATH" (a' la' PYTHONPATH) holding a colon separated (or semicolon separated on Windows) list of directories where bash will look for sourced non-absolute files (even if they contain a pathname separator) before (possibly) performing a lookup in $PATH and then in the current directory. Does this sounds sensible, or would it add too much complexity and/or confusion?
Regards, Stefano
