mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-17 15:01:40 +02:00
48356: clarify (the intended) behaviour for the two anchor forms of matching control
This commit is contained in:
parent
ad7948611c
commit
714864a87b
2 changed files with 12 additions and 2 deletions
|
@ -1,3 +1,8 @@
|
||||||
|
2021-04-02 Oliver Kiddle <opk@zsh.org>
|
||||||
|
|
||||||
|
* 48356: Doc/Zsh/compwid.yo: clarify (the intended)
|
||||||
|
behaviour for the two anchor forms of matching control
|
||||||
|
|
||||||
2021-04-01 Daniel Shahaf <d.s@daniel.shahaf.name>
|
2021-04-01 Daniel Shahaf <d.s@daniel.shahaf.name>
|
||||||
|
|
||||||
* unposted: Etc/BUGS: Add 39319, a named-file process
|
* unposted: Etc/BUGS: Add 39319, a named-file process
|
||||||
|
|
|
@ -959,6 +959,9 @@ As tt(l), tt(L), tt(b) and tt(B), with the difference that the command
|
||||||
line and trial completion patterns are anchored on the right side.
|
line and trial completion patterns are anchored on the right side.
|
||||||
Here an empty var(ranchor) and the tt(e) and tt(E) forms force the
|
Here an empty var(ranchor) and the tt(e) and tt(E) forms force the
|
||||||
match to the end of the command line or trial completion string.
|
match to the end of the command line or trial completion string.
|
||||||
|
|
||||||
|
In the form where var(lanchor) is given, the var(lanchor) only needs
|
||||||
|
to match the trial completion string.
|
||||||
)
|
)
|
||||||
item(tt(x:))(
|
item(tt(x:))(
|
||||||
This form is used to mark the end of matching specifications:
|
This form is used to mark the end of matching specifications:
|
||||||
|
@ -1022,8 +1025,10 @@ any number of characters in the trial completion. In this case the
|
||||||
pattern must be anchored (on either side); in the case of a single
|
pattern must be anchored (on either side); in the case of a single
|
||||||
star, the var(anchor) then determines how much of the trial completion
|
star, the var(anchor) then determines how much of the trial completion
|
||||||
is to be included DASH()- only the characters up to the next appearance of
|
is to be included DASH()- only the characters up to the next appearance of
|
||||||
the anchor will be matched. With two stars, substrings matched by the
|
the anchor will be matched. With two stars, substrings matched by
|
||||||
anchor can be matched, too.
|
the anchor can be matched, too. In the forms that include two
|
||||||
|
anchors, `tt(*)' can match characters from the additional anchor
|
||||||
|
DASH()- var(lanchor) with tt(r) or var(ranchor) with tt(l).
|
||||||
|
|
||||||
Examples:
|
Examples:
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue