From: Bart Schaefer <schaefer@brasslantern.com>
To: linuxtechguy@gmail.com
Cc: devs <zsh-workers@zsh.org>
Subject: Re: prompt colors bug? also possible feature add
Date: Tue, 22 Aug 2023 21:20:50 -0700 [thread overview]
Message-ID: <CAH+w=7YZ-mrpB-ofHROLpp+125fQkqZqEeYsR8KSGWNZiNH_Ww@mail.gmail.com> (raw)
In-Reply-To: <CA+rB6GK6Zji-QOkxLkQOgBYxCtwjr-g62DjGojSgdvUJwToN+Q@mail.gmail.com>
On Tue, Aug 22, 2023 at 5:37 PM Jim <linux.tech.guy@gmail.com> wrote:
>
> Not sure if I'm barking up the wrong tree ...
Not exactly ... previously I was pointing out that promises made by
the colors function have nothing to do with promises made by the
builtin prompt code.
> I guess the next questions is, does it only work with
> fade?
That's the only one that references it directly rather than by user
configuration, but it's the reason it appears in the colors arrays.
> Is there any consideration of adding bright-<color> to prompts? Just curious.
It has not been directly discussed. That doesn't mean it couldn't
happen if someone wanted to put in the effort. To the extent that
related things considered, it was decided that providing color numbers
was sufficient; color names are a throwback to when there were only
about 16 of them. Sadly most of the prompt themes are from a similar
time, there haven't been any new ones contributed for some years.
next prev parent reply other threads:[~2023-08-23 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 22:18 Jim
2023-08-17 23:23 ` Bart Schaefer
2023-08-23 0:37 ` Jim
2023-08-23 4:20 ` Bart Schaefer [this message]
2023-08-23 12:42 ` Jim
2023-08-24 3:45 ` Bart Schaefer
2023-09-20 1:15 ` Jim
2023-09-20 1:56 ` Bart Schaefer
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=7YZ-mrpB-ofHROLpp+125fQkqZqEeYsR8KSGWNZiNH_Ww@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).