From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: region_highlight cancels styles set in zle_highlight
Date: Mon, 7 Sep 2015 02:08:14 +0000 [thread overview]
Message-ID: <20150907020814.GB6263@tarsus.local2> (raw)
In-Reply-To: <20150906182230.27d259eb@ntlworld.com>
Peter Stephenson wrote on Sun, Sep 06, 2015 at 18:22:30 +0100:
> On Sat, 5 Sep 2015 10:44:49 +0000
> Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > How do $zle_highlight and $region_highlight interact? Which one takes
> > precedence if a certain byte range is covered by both?
>
> The special forms of highlight (the ones that apply to regions, so not,
> for example, unprintable characters) are treated as the initial set of
> entries in the array of highlights to apply, with any user-specified
> ones in region_highlight following in order, with later values
> overriding earlier ones.
Thanks. Patch to doc this:
diff --git a/Doc/Zsh/zle.yo b/Doc/Zsh/zle.yo
index 4e93695..22e8111 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))(
@@ -2521,6 +2526,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), 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.
next prev parent reply other threads:[~2015-09-07 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 10:44 Daniel Shahaf
2015-09-06 17:22 ` Peter Stephenson
2015-09-07 2:08 ` Daniel Shahaf [this message]
2015-09-07 8:48 ` Peter Stephenson
2015-09-07 21:21 ` Daniel Shahaf
-- strict thread matches above, loose matches on Subject: below --
2011-06-01 15:57 Mikael Magnusson
2011-06-01 15:59 ` Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150907020814.GB6263@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).