Re: PATH vs current dir and dir sure to be not existing

2024-09-28 Thread tlaronde
On Sat, Sep 28, 2024 at 06:24:58PM +0700, Robert Elz wrote: > Date:Sat, 28 Sep 2024 10:33:55 +0200 > From: > Message-ID: > > | This does mean that one user setting a PATH with variables: > | > | PATH="/bin:/usr/bin:$MYSCRIPTS:/usr/pkg/bin" > | > | if MYSCRIP

Re: PATH vs current dir and dir sure to be not existing

2024-09-28 Thread Robert Elz
Date:Sat, 28 Sep 2024 10:33:55 +0200 From: Message-ID: | This does mean that one user setting a PATH with variables: | | PATH="/bin:/usr/bin:$MYSCRIPTS:/usr/pkg/bin" | | if MYSCRIPTS is not defined, will end up including the current working | dir in his PA

PATH vs current dir and dir sure to be not existing

2024-09-28 Thread tlaronde
POSIX mandates that an empty dir in the PATH env variable (i.e. an initial or terminal colon, or an empty entry "...::...") be treated as meaning the current working dir, allowing to try to execute the searched utility there. This does mean that one user setting a PATH with variables: PATH="/bin: