From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Phil Pennock <zsh-workers+phil.pennock@spodhuis.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Possible bug: HASH_CMDS has no observable effect
Date: Fri, 11 Sep 2020 17:01:48 +0200 [thread overview]
Message-ID: <CAN=4vMrFhmKitKbdPdabZ1Ey9cjmEf62GVaGVMxn6T9AjZVc8Q@mail.gmail.com> (raw)
In-Reply-To: <20200911144852.GA1669764@fullerene.field.pennock-tech.net>
On Fri, Sep 11, 2020 at 4:48 PM Phil Pennock
<zsh-workers+phil.pennock@spodhuis.org> wrote:
>
> On 2020-09-11 at 10:21 +0200, Roman Perepelitsa wrote:
> > From the documentation for HASH_CMDS option:
> >
> > Note the location of each command the first time it is executed.
> > Subsequent invocations of the same command will use the saved
> > location, avoiding a path search. If this option is unset, no path
> > hashing is done at all. However, when CORRECT is set, commands
> > whose names do not appear in the functions or aliases hash tables
> > are hashed in order to avoid reporting them as spelling errors.
>
> So, if and only if CORRECT is set, then non-present commands will be
> remembered as not present.
Could you clarify how this statement is related to my bug report?
In case this wasn't clear, in my bug report the output of the
following two commands is not what I expect:
# print $+commands[rsync]
0
# hash | grep rsync
#
The expected output:
# print $+commands[rsync]
1
# hash | grep rsync
rsync=/usr/bin/rsync
#
The reason why I expect this output is because I've invoked rsync
right before these two commands while HASH_CMDS was in effect.
Roman.
next prev parent reply other threads:[~2020-09-11 15:02 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 [this message]
2020-09-11 16:10 ` Phil Pennock
2020-09-11 16:33 ` Roman Perepelitsa
2020-09-11 21:10 ` Bart Schaefer
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='CAN=4vMrFhmKitKbdPdabZ1Ey9cjmEf62GVaGVMxn6T9AjZVc8Q@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=zsh-workers+phil.pennock@spodhuis.org \
--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).