From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Possible bug: HASH_CMDS has no observable effect
Date: Fri, 11 Sep 2020 14:10:33 -0700 [thread overview]
Message-ID: <CAH+w=7Y2VQpidVcinSXkQQqng0XjOwYtWL7a8jiYFx+te7fQCw@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMq-prFqopCW8apuYO8YUnuKL8G=WX+jBXFwgiFkfY=5Pw@mail.gmail.com>
On Fri, Sep 11, 2020 at 9:33 AM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> Why isn't rsync hashed the first time it's executed?
This is usually because of HASH_DIRS:
Whenever a command name is hashed, hash the directory containing
it, as well as all directories that occur earlier in the path.
Once the cache has been pre-populated by hashing a directory,
HASH_CMDS stops attempting to search that directory for new additions.
A "rehash" is needed to discard the cached directory and reload any
new commands that are now contained therein.
If you unset HASH_DIRS you might get what you want.
A complication of this is that the completion system also invokes
command hashing in order to be able to use the $commands associative
array. So if you use completion at all, you might also find that
command (re)hashing works differently than in a "zsh -f" shell. Refer
to the description of "rehash" under "Standard Styles".
next prev parent reply other threads:[~2020-09-11 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 8:21 Roman Perepelitsa
2020-09-11 14:48 ` Phil Pennock
2020-09-11 15:01 ` Roman Perepelitsa
2020-09-11 16:10 ` Phil Pennock
2020-09-11 16:33 ` Roman Perepelitsa
2020-09-11 21:10 ` Bart Schaefer [this message]
2020-09-12 7:02 ` Roman Perepelitsa
2020-09-12 8:35 ` Bart Schaefer
2020-09-12 8:49 ` Roman Perepelitsa
2020-09-12 20:41 ` Bart Schaefer
2020-09-12 20:43 ` Bart Schaefer
2020-09-13 9:31 ` Roman Perepelitsa
2020-09-13 22:24 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7Y2VQpidVcinSXkQQqng0XjOwYtWL7a8jiYFx+te7fQCw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).