zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: End boldface also ends background color
Date: Thu, 24 Mar 2016 17:23:25 -0700	[thread overview]
Message-ID: <CAH+w=7aQ_mkg3oWPtzMEn0zSRZTDDqnK8o2hKgruhEezBAU_9A@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3T9gGLaDrOqSzC7_71bO090=guTCoYAxW76=CKZo9-Rng@mail.gmail.com>

On Thu, Mar 24, 2016 at 3:43 PM, Mikael Magnusson <mikachu@gmail.com> wrote:
>
> Using $fg from colors doesn't buy you anything over using the builtin
> prompt sequences though. They also do not have an un-bold sequence.

Strictly speaking, $fg doesn't have a simple bold sequence either --
you have to use e.g. $fg_bold[red] and $fg_no_bold[red], so if you
stick to the intended model you do have un-bold.

There is $bold_color but it's only thrown in there because of the
comment about black and white being less than pure in some terminal
color palettes.  There aren't escape codes created by the colors
function for standout, underline, faint, etc. either, but we could add
e.g. $normal_color if that's the only issue.


      reply	other threads:[~2016-03-25  0:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 19:44 Dominik Ritter
2016-03-22 21:00 ` Mikael Magnusson
2016-03-24  1:53   ` Bart Schaefer
2016-03-24 10:38     ` Peter Stephenson
2016-03-24 14:53       ` Danek Duvall
2016-03-24 17:26         ` Bart Schaefer
2016-03-24 18:08           ` Danek Duvall
2016-03-24 17:21       ` Mikael Magnusson
2016-03-24 17:33       ` Bart Schaefer
2016-03-24 17:39         ` Peter Stephenson
2016-03-24 18:00           ` Bart Schaefer
     [not found]     ` <20160324103837.678f2f36__45846.6877033517$1458816008$gmane$org@pwslap01u.europe.root.pri>
2016-03-24 18:20       ` Stephane Chazelas
2016-03-24 21:34         ` Bart Schaefer
2016-03-24 22:43           ` Mikael Magnusson
2016-03-25  0:23             ` Bart Schaefer [this message]

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=7aQ_mkg3oWPtzMEn0zSRZTDDqnK8o2hKgruhEezBAU_9A@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=mikachu@gmail.com \
    --cc=zsh-users@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).