mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-11 13:01:28 +02:00
users/18644: bindkey -s doc should have forward reference.
Indicate there is documentation for the argument strings.
This commit is contained in:
parent
fd4ac0a8c2
commit
86873edea9
2 changed files with 6 additions and 0 deletions
|
@ -1,5 +1,8 @@
|
||||||
2014-03-20 Peter Stephenson <p.stephenson@samsung.com>
|
2014-03-20 Peter Stephenson <p.stephenson@samsung.com>
|
||||||
|
|
||||||
|
* users/18644: Doc/Zsh/zle.yo: bindkey -s doc should refer to
|
||||||
|
documentation for argument interpretation.
|
||||||
|
|
||||||
* Completion/Unix/Command/_perforce: finally, after more than
|
* Completion/Unix/Command/_perforce: finally, after more than
|
||||||
ten years, complete depots after // in file paths as it always
|
ten years, complete depots after // in file paths as it always
|
||||||
should have done.
|
should have done.
|
||||||
|
|
|
@ -252,6 +252,9 @@ Bind each var(in-string) to each var(out-string).
|
||||||
When var(in-string) is typed, var(out-string) will be
|
When var(in-string) is typed, var(out-string) will be
|
||||||
pushed back and treated as input to the line editor.
|
pushed back and treated as input to the line editor.
|
||||||
When tt(-R) is also used, interpret the var(in-string)s as ranges.
|
When tt(-R) is also used, interpret the var(in-string)s as ranges.
|
||||||
|
|
||||||
|
Note that both var(in-string) and var(out-string) are subject to the same
|
||||||
|
form of interpretation, as described below.
|
||||||
)
|
)
|
||||||
item(var(in-string command) ...)(
|
item(var(in-string command) ...)(
|
||||||
Bind each var(in-string) to each var(command).
|
Bind each var(in-string) to each var(command).
|
||||||
|
|
Loading…
Reference in a new issue