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
