summary refs log tree commit diff
path: root/Doc/Zsh
diff options
context:
space:
mode:
authorPeter Stephenson <p.stephenson@samsung.com>2019-03-19 14:22:34 +0000
committerPeter Stephenson <p.stephenson@samsung.com>2019-03-19 14:22:34 +0000
commit876dccfe739fd137dc18527bec9c08c8a303e8a6 (patch)
treee00474207c7f6aee30dbc2b0a24b902274f648e4 /Doc/Zsh
parent084bf17c4bc28a2a651c69fdc9a5bdd6473c3b04 (diff)
downloadzsh-876dccfe739fd137dc18527bec9c08c8a303e8a6.tar.gz
zsh-876dccfe739fd137dc18527bec9c08c8a303e8a6.tar.xz
zsh-876dccfe739fd137dc18527bec9c08c8a303e8a6.zip
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.
Diffstat (limited to 'Doc/Zsh')
-rw-r--r--Doc/Zsh/builtins.yo6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
index a926395ad..d7b6e88fa 100644
--- a/Doc/Zsh/builtins.yo
+++ b/Doc/Zsh/builtins.yo
@@ -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.