From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: 'whence' anomaly.
Date: Mon, 24 Mar 2014 23:25:23 -0700 [thread overview]
Message-ID: <140324232523.ZM5058@torch.brasslantern.com> (raw)
In-Reply-To: <5330F3B0.7030704@eastlink.ca>
On Mar 24, 8:10pm, Ray Andrews wrote:
} Subject: Re: 'whence' anomaly.
}
} On 03/24/2014 03:48 PM, Bart Schaefer wrote:
} >
} > "whence -m" searches, but does not populate, the command hash table.
Hmm, I seem to be wrong about that. I just double-checked the code
(which I didn't bother to do before) and there is a call there to fill
the command hash table.
Furthermore, I can't reproduce Ray's original example now, though I'm
pretty certain I did at least once.
} > Thus if the NO_HASH_CMDS option is set, "whence -m" does not work
} > at all. [*]
And this is only partly true. :-( You have to both set NO_HASH_CMDS
_and_ erase the hash table with e.g. 'unhash -m \*' to break this,
otherwise the aforementioned code in whence fills the table regardless
of NO_HASH_CMDS.
So I apologize for the red herrings.
} Yikes, more ifs buts and maybes. Is there some way to get a reliable
} result?
Based on what I just (re)discovered, it seems necessary to go out of
the way to get an UNreliable result. What are the circumstances in
which you get nothing from 'whence -m', again?
next prev parent reply other threads:[~2014-03-25 6:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 14:43 Segregating a Global Alias zzapper
2014-03-24 17:22 ` Bart Schaefer
2014-03-24 17:34 ` zzapper
2014-03-24 17:47 ` zzapper
2014-03-24 18:04 ` Re[2]: " Manuel Presnitz
2014-03-25 12:28 ` zzapper
2014-03-24 18:11 ` Paul Johnson
2014-03-24 18:19 ` 'whence' anomaly Ray Andrews
2014-03-24 22:48 ` Bart Schaefer
2014-03-25 3:10 ` Ray Andrews
2014-03-25 6:25 ` Bart Schaefer [this message]
2014-03-25 15:32 ` Ray Andrews
2014-03-24 22:36 ` Segregating a Global Alias Bart Schaefer
2014-03-25 1:56 ` Bart Schaefer
2014-03-25 14:07 ` zzapper
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=140324232523.ZM5058@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).