all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
Subject: Re: master 11f10dc0d0b: Update etc/rgb.txt from X.Org upstream
Date: Sun, 15 Oct 2023 15:59:05 +0800	[thread overview]
Message-ID: <87bkd08gfq.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmCC=WS+drfJfQbJWSQi+09S=PeUP3xnL1VCDiGgcTAJA@mail.gmail.com> (Stefan Kangas's message of "Sun, 15 Oct 2023 00:43:45 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> I'm not quite following.  Are you referencing aesthetic differences or
> older X server behaviors?  Could you clarify the reason behind
> maintaining this difference with X.Org?

Because circa 2020 X.Org is not the only X server we support, and it is
thus our duty to deter Lisp code from using color names exclusive to it.

One manner in which that duty is fulfilled is by omitting such names
from ports that don't consult the display server's color database,
namely those which load colors from rgb.txt.



  reply	other threads:[~2023-10-15  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169731145392.6616.366366221046340825@vcs2.savannah.gnu.org>
     [not found] ` <20231014192414.36BEBC09BCA@vcs2.savannah.gnu.org>
2023-10-15  1:10   ` master 11f10dc0d0b: Update etc/rgb.txt from X.Org upstream Po Lu
2023-10-15  5:50     ` Eli Zaretskii
2023-10-15  7:43       ` Stefan Kangas
2023-10-15  7:59         ` Po Lu [this message]
2023-10-15  9:38         ` Mattias Engdegård
2023-10-15  7:09     ` Stefan Kangas
2023-10-15  7:41       ` Po Lu
2023-10-16 14:33         ` Stefan Kangas
2023-10-16 23:49           ` Po Lu
2023-10-17  9:24             ` Stefan Kangas
2023-10-17 10:45               ` Po Lu
2023-10-17 11:10               ` Eli Zaretskii

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=87bkd08gfq.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.