diff options
Diffstat (limited to 'Doc/Zsh')
| -rw-r--r-- | Doc/Zsh/expn.yo | 14 | ||||
| -rw-r--r-- | Doc/Zsh/zle.yo | 25 |
2 files changed, 38 insertions, 1 deletions
diff --git a/Doc/Zsh/expn.yo b/Doc/Zsh/expn.yo index d44b40a3b..5ea8610f2 100644 --- a/Doc/Zsh/expn.yo +++ b/Doc/Zsh/expn.yo @@ -1956,6 +1956,20 @@ ifzman(the zmanref(zshparam) manual page)\ ifnzman(noderef(Parameters Used By The Shell))\ . ) +item(tt([:INCOMPLETE:]))( +Matches a byte that starts an incomplete multibyte character. +Note that there may be a sequence of more than one bytes that +taken together form the prefix of a multibyte character. To +test for a potentially incomplete byte sequence, use the pattern +`tt([[:INCOMPLETE:]]*)'. This will never match a sequence starting +with a valid multibyte character. +) +item(tt([:INVALID:]))( +Matches a byte that does not start a valid multibyte character. +Note this may be a continuation byte of an incomplete multibyte +character as any part of a multibyte string consisting of invalid and +incomplete multibyte characters is treated as single bytes. +) item(tt([:WORD:]))( The character is treated as part of a word; this test is sensitive to the value of the tt(WORDCHARS) parameter diff --git a/Doc/Zsh/zle.yo b/Doc/Zsh/zle.yo index 4e9369508..2c539c460 100644 --- a/Doc/Zsh/zle.yo +++ b/Doc/Zsh/zle.yo @@ -955,6 +955,11 @@ any predisplay string should be highlighted in bold. Note that the effect of tt(region_highlight) is not saved and disappears as soon as the line is accepted. + +The final highlighting on the command line depends on both tt(region_highlight) +and tt(zle_highlight); see +ifzman(the section CHARACTER HIGHLIGHTING below)\ +ifnzman(noderef(Character Highlighting)) for details. ) vindex(UNDO_CHANGE_NO) item(tt(UNDO_CHANGE_NO) (integer))( @@ -1000,6 +1005,18 @@ executed; the second argument that followed tt(zle -C) when the widget was defined. This is the name of a builtin completion widget. For widgets defined with tt(zle -N) this is set to the empty string. Read-only. ) +vindex(YANK_ACTIVE) +vindex(YANK_START) +vindex(YANK_END) +xitem(tt(YANK_ACTIVE) (integer)) +xitem(tt(YANK_START) (integer)) +item(tt(YANK_END) (integer))( +These three parameters indicate whether text has just been yanked (pasted) +into the buffer. tt(YANK_START) and tt(YANK_END) are in the same unit sas +tt(CURSOR), and are only valid when tt(YANK_ACTIVE) is non-zero. + +All three are read-only. +) vindex(ZLE_STATE) item(tt(ZLE_STATE) (scalar))( Contains a set of space-separated words that describe the current tt(zle) @@ -1018,7 +1035,7 @@ The substrings are sorted in alphabetical order so that if you want to test for two specific substrings in a future-proof way, you can do match by doing: -example(if [[ $ZLE_STATE == *insert*globalhistory* ]]; then ...; fi) +example(if [[ $ZLE_STATE == *globalhistory*insert* ]]; then ...; fi) ) enditem() @@ -2521,6 +2538,12 @@ Following a command to paste text, the characters that were inserted. ) enditem() +When tt(region_highlight) is set, the contexts that describe a region DASH()- +tt(isearch), tt(region), tt(suffix), and tt(paste) DASH()- +are applied first, then tt(region_highlight) is applied, then the remaining +tt(zle_highlight) contexts are applied. If a particular character is +affected by multiple specifications, the last specification wins. + tt(zle_highlight) may contain additional fields for controlling how terminal sequences to change colours are output. Each of the following is followed by a colon and a string in the same form as for key bindings. |