[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: command_not_found_handle not run when PATH is empty
|
From: |
Chet Ramey |
|
Subject: |
Re: command_not_found_handle not run when PATH is empty |
|
Date: |
Thu, 16 Mar 2023 11:30:29 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 |
On 3/9/23 5:42 PM, Moshe Looks wrote:
Thank you this is very illuminating and makes it clear that my naive
one-line fix would be inappropriate. Given the current state of
affairs there is really no good reason for PATH to ever be unset or
set to empty vs. explicitly set to '.', right? So might be worth
spelling out in the docs that this is inadvisable :).
There shouldn't be any difference between PATH=. and PATH=, but why not
use the former and make your intent clear?
Behavior varies with `unset PATH', so it makes sense not to use it. The
Bourne shell didn't even allow PATH to be unset.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/