unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tony Zorman <tonyzorman@mailbox.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, info@protesilaos.com
Subject: Re: Ansi-color uses the same values for fore- and background colours
Date: Wed, 09 Aug 2023 18:18:19 +0200	[thread overview]
Message-ID: <878rakmbp0.fsf@hyperspace> (raw)
In-Reply-To: <83msz0l4zb.fsf@gnu.org>

On Wed, Aug 09 2023 16:28, Eli Zaretskii wrote:
>> From: Tony Zorman <tonyzorman@mailbox.org>
>> Date: Wed, 09 Aug 2023 14:10:44 +0200
>> 
>> by default, all of the `ansi-color-«COLOUR»' faces (defined in
>> `ansi-color.el') set the foreground and background colour to the exact
>> same value.
>
> I believe this is intentional: that's how ANSI SGR sequences work on
> terminals, right?

I'm a bit rusty with my escape sequences; they don't hard-code colours,
right? I thought that e.g. `ESC[31m' just means "colour the foreground
on some kind of red", `ESC[41m' means the same for the background, and
then the terminal interprets this appropriately. Is there actually some
standard that says these two colours have to be the same, or am I
missing some other detail? I suppose terminals implementing this could
choose to use the same value for both colours, and maybe most of them
did.

Either way, I guess the modus-themes shouldn't run into any issues when
diverging from this.

Thanks!

-- 
Tony Zorman | https://tony-zorman.com/



  reply	other threads:[~2023-08-09 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 12:10 Ansi-color uses the same values for fore- and background colours Tony Zorman
2023-08-09 13:28 ` Eli Zaretskii
2023-08-09 16:18   ` Tony Zorman [this message]
2023-08-09 16:31     ` Eli Zaretskii
2023-08-09 16:46   ` Jim Porter
2023-08-09 16:51 ` Jim Porter
2023-08-10  3:59   ` Tony Zorman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878rakmbp0.fsf@hyperspace \
    --to=tonyzorman@mailbox.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=info@protesilaos.com \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).