From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh workers <zsh-workers@zsh.org>
Subject: PATCH: explicitly document need for # in colour hex triplets
Date: Sun, 15 Dec 2019 14:17:12 +0100 [thread overview]
Message-ID: <13303-1576415832.545696@VG4M.ZpcM.KQAL> (raw)
In-Reply-To: <13303-1576415832.545696.ref@VG4M.ZpcM.KQAL>
Based on a user question on an external forum, we should explicitly
spell out the need for the # character when specifying colours as
hex triplets. It is already explicit a couple of paragraphs before
this but in the context of zle_highlight rather than prompts.
Note that it is necessary for us to require the # because 3 digit colour
numbers already refer to colours in the 256 colour palette. With 6
digits we might allow it to be omitted but I don't think it'd be a good
idea.
Oliver
diff --git a/Doc/Zsh/zle.yo b/Doc/Zsh/zle.yo
index 0986e5390..c928b8ca2 100644
--- a/Doc/Zsh/zle.yo
+++ b/Doc/Zsh/zle.yo
@@ -2729,10 +2729,10 @@ limited to 256 (i.e. the range 0 to 255).
Some modern terminal emulators have support for 24-bit true colour (16
million colours). In this case, the hex triplet format can be used. This
-consists of either a three or six digit hexadecimal number describing
-the red, green and blue components of the colour. Hex triplets can also
-be used with 88 and 256 colour terminals via the tt(zsh/nearcolor)
-module (see ifzman(zmanref(zshmodules))\
+consists of a `tt(#)' followed by either a three or six digit hexadecimal
+number describing the red, green and blue components of the colour. Hex
+triplets can also be used with 88 and 256 colour terminals via the
+tt(zsh/nearcolor) module (see ifzman(zmanref(zshmodules))\
ifnzman(noderef(The zsh/nearcolor Module))\
).
parent reply other threads:[~2019-12-15 21:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <13303-1576415832.545696.ref@VG4M.ZpcM.KQAL>]
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=13303-1576415832.545696@VG4M.ZpcM.KQAL \
--to=okiddle@yahoo.co.uk \
--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).