zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: devs <zsh-workers@zsh.org>
Subject: Re: possible PATCH to colors function
Date: Mon, 17 Jul 2023 11:40:31 -0700	[thread overview]
Message-ID: <CAH+w=7Ygu8gEh9M4p-3ohvweoyoQOqyN+ntNB-MSbywXb_aOLQ@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6GJb_Vn8yXU8XfQnvACB3c5Fpfp6DtFNGobC42DjcAqpsg@mail.gmail.com>

On Mon, Jul 17, 2023 at 10:45 AM Jim <linux.tech.guy@gmail.com> wrote:
>
> [bf]g_bold for both <color> and <bright-color> produces  the same result.
>   bold with the same "intensity" for both <color> or <bright-color>

I get different results for all three faint/normal/bright, in both
Gnome terminal and xterm.  I'm reluctant to change the default
appearance of "normal" everywhere in order to accommodate terminals
that (seemlngly) don't fully support "bright".

Just for interest, try this:
% colors
% print -r $'\e['$color[faint]\;${color[bright-red]}m88888${reset_color}\
$'\e['${color[red]}m88888${reset_color}\
$'\e['${color[bright-red]}m88888${reset_color}

(or with $'\n' before each backslash).  Do you really see no change
from red to bright-red?

I'd be more inclined to create a $fg[faint-*] etc. to match the
addition of $fg[bright-*] although with the bright variants there's no
alternate way to obtain them.


  reply	other threads:[~2023-07-17 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 17:44 Jim
2023-07-17 18:40 ` Bart Schaefer [this message]
2023-07-17 18:48   ` Bart Schaefer
2023-07-18 10:26     ` Jim
2023-07-18 11:18       ` Roman Perepelitsa
2023-07-18 12:48         ` Jim

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='CAH+w=7Ygu8gEh9M4p-3ohvweoyoQOqyN+ntNB-MSbywXb_aOLQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=linuxtechguy@gmail.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).