On Tue, Aug 31, 2021 at 11:19:10AM -0400, Steve Dondley wrote: > > >This sounds like a stale-hash situation. According to my understanding, > >the shell will typically keep a cache of what path it found a given > >command at when it checked for that command in $PATH, so it > >doesn't have > >to re-do the filesystem accesses on every run of the command; this > >mapping of known paths to commands is apparently referred to as a > >set of > >hashes. > > > >I'm not familiar with zsh, but in bash, you could try 'hash -d fzf' to > >drop the cached known path for fzf (so that the next check will look it > >up again from scratch), or even 'hash -r' to forget *all* the known > >paths for everything. > > Ah, yes, some kind of zsh command caching appears to be implemented. > But rather than guessing at the correct zsh command, logging in with > a totally new shell corrected the problem and "which" now shows the > expected path.
There's `hash -r' for that (bash, dash). I'd bet that zsh has something along that lines, too. Cheers - t
signature.asc
Description: Digital signature