unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 11f10dc0d0b: Update etc/rgb.txt from X.Org upstream
Date: Tue, 17 Oct 2023 07:49:25 +0800	[thread overview]
Message-ID: <s0dil76i0vu.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmnJXL=ic-jcwBQN3qoSqLtW16apLj-1ExQYCFM1xkhWw@mail.gmail.com> (Stefan Kangas's message of "Mon, 16 Oct 2023 14:33:40 +0000")

Stefan Kangas <stefankangas@gmail.com> writes:

> While using portable colors is a concern, it seems orthogonal.  X.Org
> ships with these colors, and as things stand, nothing is stopping them
> from being used.  We could perhaps recommend against using them, and
> not much else.

We shouldn't distribute non-standard color files in the first place:
users should have no occasion to use them, so the less places they are
mentioned or available in, the better.

> Reverting will mean that these colors won't work for users on some of
> our most commonly used platforms.  That's all.  Is it good practice to
> leave such things broken on some platforms, in the hope that it will
> be enough to provoke Emacs Lisp developers to fix it on some others?

Yes, since "web" colors are easily specified through their RGB values,
and "x11" colors are identical to their unprefixed progenitors.



  reply	other threads:[~2023-10-16 23:49 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
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 [this message]
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

  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=s0dil76i0vu.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --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 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).