all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 11f10dc0d0b: Update etc/rgb.txt from X.Org upstream
Date: Tue, 17 Oct 2023 09:24:20 +0000	[thread overview]
Message-ID: <CADwFkmneJnFjNrYQm0rH+gOwzzH=yV7TLC2mE97GBohnodSU2w@mail.gmail.com> (raw)
In-Reply-To: <s0dil76i0vu.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> 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:

I don't know which standard this is referring to.  XFree86R6?

> users should have no occasion to use them, so the less places they are
> mentioned or available in, the better.

AFAIK, nothing is stopping their use on X.Org so, whatever you and I
might think of it, it is clear that users can and will use them.

>> 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.

I didn't ask if alternatives existed, but if we should leave this
non-working on some of our most commonly used systems for the benefit of
Solaris users (the only example given so far).  I see no catastrophe
either way, to be quite honest.

Anyways, you seem to care more strongly than I do, so I'll leave the
decision to you.  I remain unconvinced, but we can agree to disagree.
For next time, please consider that it might be more collaborative to
wait with reverting, to make sure that all viewpoints are fully
considered.



  reply	other threads:[~2023-10-17  9:24 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
2023-10-17  9:24             ` Stefan Kangas [this message]
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='CADwFkmneJnFjNrYQm0rH+gOwzzH=yV7TLC2mE97GBohnodSU2w@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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.