mirror of
git://git.code.sf.net/p/zsh/code
synced 2024-05-31 04:16:06 +02:00
Update doc from previous commit.
Make it clear it's commands whose names begin with a / that aren't hashed. Obviously commands whose paths begin with a / are OK, duh.
This commit is contained in:
parent
084bf17c4b
commit
876dccfe73
|
@ -1,5 +1,7 @@
|
|||
2019-03-19 Peter Stephenson <p.stephenson@samsung.com>
|
||||
|
||||
* unposted: Make the doc change in the foregoing clearer.
|
||||
|
||||
* Charles Blake: 44132: Src/exec.c, Doc/Zsh/builtins.yo: don't
|
||||
hash commands beginning with a '/'.
|
||||
|
||||
|
|
|
@ -988,9 +988,9 @@ The choice of hash table to work on is determined by the tt(-d) option;
|
|||
without the option the command hash table is used, and with the option the
|
||||
named directory hash table is used.
|
||||
|
||||
Command paths starting with a tt(/) are never hashed, whether by explicit
|
||||
use of the tt(hash) command or otherwise, but are always found
|
||||
by direct look up in the file system.
|
||||
A command var(name) starting with a tt(/) is never hashed, whether by
|
||||
explicit use of the tt(hash) command or otherwise. Such a command
|
||||
is always found by direct look up in the file system.
|
||||
|
||||
Given no arguments, and neither the tt(-r) or tt(-f) options,
|
||||
the selected hash table will be listed in full.
|
||||
|
|
Loading…
Reference in New Issue