zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
	Daniel Shahaf <d.s@daniel.shahaf.name>,
	 Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Functions/Misc/colors vs. region_highlight
Date: Tue, 3 Nov 2020 20:54:12 +0200	[thread overview]
Message-ID: <CAHLkEDv-vnjajmXgF6CnVwMOigj3u80ajeZnw=YN26qqLaFWYw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YDH-WPzaPJ=TfyN_mAmaA+jHthdhZOrP-rnQL2XzsLLA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]

On Sat, 24 Oct 2020 at 03:50, Bart Schaefer <schaefer@brasslantern.com>
wrote:

> You're correct that "standout" doesn't match the terminology in
> ECMA-48.  The use of "standout" was chosen to follow the terminology
> in prompt strings, I believe.
>
> This matched the behavior of most terminals at the time (notice
> ${(k)color[(r)standout]} is actually from Sven all the way back in
> 2001).  Also, there's no way to directly reference an escape sequence
> for any of the "Attribute Codes" (they aren't in the $fg / $bg
> hashes), so those values are mostly there for commentary value.
>
> I would have no objection to adding "italic"/"no-italic" to the color
> hash.  It also appears standout would more accurately be tied to
> reverse-video now, but because the keys of the hash are the numeric
> codes we can only have one or the other.
>

Would it be possible to drop `standout` (as it's rather ambiguous) and
instead add both `italic` and `reverse`? They both have `terminfo` entries.

It would be great if Zsh could eventually support the same highlighting
keywords as [Git does](
https://www.git-scm.com/docs/git-config#Documentation/git-config.txt-color),
but I guess that's a long way off.

[-- Attachment #2: Type: text/html, Size: 1725 bytes --]

  reply	other threads:[~2020-11-03 18:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12  9:22 region_highlight converts `fg=default` to `none`, which is not the same Marlon Richert
2020-10-13 11:05 ` Roman Perepelitsa
2020-10-14  5:12   ` Marlon Richert
2020-10-14 20:46   ` Daniel Shahaf
2020-10-15  7:37     ` Roman Perepelitsa
2020-10-15 16:58       ` Marlon Richert
2020-10-15 17:09         ` Roman Perepelitsa
2020-10-16 13:36           ` Daniel Shahaf
2020-10-24  1:34           ` Oliver Kiddle
2020-10-24  6:42             ` Roman Perepelitsa
2020-10-16 13:28       ` Daniel Shahaf
2020-10-16 15:50         ` Bart Schaefer
2020-10-22 19:58           ` Marlon Richert
2020-10-22 23:28             ` Daniel Shahaf
2020-10-23  8:08             ` Roman Perepelitsa
2020-10-23  9:24               ` Marlon Richert
2020-10-23  9:35                 ` Roman Perepelitsa
2020-10-23 10:40                   ` Marlon Richert
2020-10-23 11:38                     ` Roman Perepelitsa
2020-10-24  0:50                       ` Functions/Misc/colors vs. region_highlight Bart Schaefer
2020-11-03 18:54                         ` Marlon Richert [this message]
2020-11-03 23:45                           ` Bart Schaefer
2020-11-04 15:47                             ` Marlon Richert
2021-04-18 21:40                         ` Bart Schaefer
2020-10-23 23:57                   ` Threading across year boundaries (was: Re: region_highlight converts `fg=default` to `none`, which is not the same) Daniel Shahaf
2021-03-31  8:26       ` region_highlight converts `fg=default` to `none`, which is not the same Marlon Richert
2021-04-10 20:33         ` Lawrence Velázquez
2021-04-13 15:20           ` Daniel Shahaf
2021-04-13 20:33             ` Roman Perepelitsa
2021-04-14 11:04               ` Daniel Shahaf
2021-05-09 20:49                 ` Lawrence Velázquez
2021-05-31  1:16                   ` Lawrence Velázquez
2021-03-31  8:24   ` Marlon Richert

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='CAHLkEDv-vnjajmXgF6CnVwMOigj3u80ajeZnw=YN26qqLaFWYw@mail.gmail.com' \
    --to=marlon.richert@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=roman.perepelitsa@gmail.com \
    --cc=schaefer@brasslantern.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).