On 3/17/14 10:19 AM, Reuben Thomas wrote:
> Only the minor performance hit it would extract on every command lookup.
>
>
> I don't understand, surely it only has a performance impact when a hashed
> file or a directory on PATH is (re)moved?
Not exactly, since it requires a check of every hashed filename retrieved
from the command hash table. I should have said every *successful*
command hash table lookup.
>
> Failing that, I'd also happily prepare a patch to simply switch the default
> to on.
Thanks; I think I can handle adding `= 1;'. :-)
I will look at doing this for the next version.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
