-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Chet Ramey on 11/21/2006 7:15 AM:
>>> Chet Ramey wrote:
When this option is on, bash has to check the hashed filename for
each hash lookup. This essentially causes the hash entry to be
deleted and re-added each time, which
Bob Proulx wrote:
>> Chet Ramey wrote:
>>> When this option is on, bash has to check the hashed filename for
>>> each hash lookup. This essentially causes the hash entry to be
>>> deleted and re-added each time, which resets the number of hits to 1.
>>> (It could probably be done without the dele
Erp... I probably thought it was getting rid of the problem I've had
in the past with ksh-type shells of retaining a bad-mapping to a file that
was no longer accessible. A minor annoyance, admittedly, but one that
entangled me a few times several (or more) years ago...
Chet Ramey wrote:
Linda
Chet Ramey wrote:
You probably have the `checkhash' shell option set.
---
Yup...didn't know about that
Posix requires
that the command hash table be transparent, in the sense that it can
only be used if the hashed command corresponds to a valid pathname.
It's designed to address the is
