Date:Mon, 28 Oct 2019 16:51:23 +0100
From:Joerg Schilling
Message-ID: <5db70e7b.yxnjo0drh2ps6v6p%joerg.schill...@fokus.fraunhofer.de>
| bosh is still a direct descendent of the Bourne Shell source code written by
| Stephen Bourne
Sure, like several other shells
Robert Elz wrote:
> | But why don't you like the "type" behavior of the Bourne Shell?
>
> As I recall it, the Bourne shell (which is the shell written and
> maintained by Steve Bourne, and distributed with the pdp-11 v7, and
> vax 32V research unix systems, anything else is a modified
Date:Mon, 28 Oct 2019 13:38:52 +0100
From:Joerg Schilling
Message-ID: <5db6e15c.IGPuYWSr17Urs/hq%joerg.schill...@fokus.fraunhofer.de>
| I am not sure whether older ksh's did behave different, but ksh93 does
| not seem to support the idea of a "tracked alias"
Robert Elz wrote:
> ps: it appears from some very brief testing that the ksh derivatives (and
> bosh) treat -h much the say you say, bash, nbsh, fbsh, and yash do not,
> zsh and dash seem not ti have a -h option at all (a desirable state IMO).
I am not sure whether older ksh's did behave
Robert Elz wrote, on 27 Oct 2019:
>
> If it hasn't already happened in some other issue/bug report that
> I'm unaware of, could we do the same thing as was done for "nolog"
> to the absurd -h option?
See bug 1063.
--
Geoff Clare
The Open Group, Apex Plaza, Forbury Road, Reading, RG1 1AX,
On 27/10/2019 19:39, Shware Systems wrote:
I thought the purpose of set -h was to ignore any previous hashing, and
do an actual path search per 2.9.1.1 for each command until set +h says
to use hashed paths again. This would be useful for apps that use a
temporary path, but reset it to
On 27/10/2019 17:16, Robert Elz wrote:
Date:Sun, 27 Oct 2019 15:44:52 +
From:Harald van Dijk
Message-ID: <01735f8e-c0ef-a1d6-f8d1-258a669d9...@gigawatt.nl>
| This could potentially be useful if the script author knows the command
| will be executed in
Date:Sun, 27 Oct 2019 15:44:52 +
From:Harald van Dijk
Message-ID: <01735f8e-c0ef-a1d6-f8d1-258a669d9...@gigawatt.nl>
| This could potentially be useful if the script author knows the command
| will be executed in multiple subshells, but never in the parent
On 27/10/2019 14:51, Robert Elz wrote:
While the subject of this message refers to 7-TC1, the page/line numbers
below refer to 7-TC2.
If it hasn't already happened in some other issue/bug report that
I'm unaware of, could we do the same thing as was done for "nolog"
to the absurd -h option?
While the subject of this message refers to 7-TC1, the page/line numbers
below refer to 7-TC2.
If it hasn't already happened in some other issue/bug report that
I'm unaware of, could we do the same thing as was done for "nolog"
to the absurd -h option?
I have no idea if it is implemented
The following issue has a resolution that has been APPLIED.
==
http://austingroupbugs.net/view.php?id=981
==
Reported By:joerg
Assigned To:
The following issue has been set as RELATED TO issue 0001207.
==
http://austingroupbugs.net/view.php?id=981
==
Reported By:joerg
Assigned
12 matches
Mail list logo
