On Sat, Sep 28, 2024 at 10:55:06AM -0700, Greg A. Woods wrote:
>
> Well, I'll be. I don't remember ever using "test -t"! I think I must
> have skipped over it entirely all these years! So I now have:
>
> if [ -t 0 -a -t 2 -a "$0" = "$SHELL" ]; then
> _interactive=true
>
At Sat, 28 Sep 2024 05:35:02 +0700, Robert Elz wrote:
Subject: Re: interactive shell detection in shrc
>
> But any current POSIX compat sh should have 'i' in $- if it is interactive.
> That is required.
Ah, but only since Issue 8.
That does clarify things, but it's rather late in the game, and i
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
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
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:
