From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master 11f10dc0d0b: Update etc/rgb.txt from X.Org upstream
Date: Tue, 17 Oct 2023 14:10:40 +0300 [thread overview]
Message-ID: <83lec1o66n.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmneJnFjNrYQm0rH+gOwzzH=yV7TLC2mE97GBohnodSU2w@mail.gmail.com> (message from Stefan Kangas on Tue, 17 Oct 2023 09:24:20 +0000)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Tue, 17 Oct 2023 09:24:20 +0000
> Cc: emacs-devel@gnu.org
>
> 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.
Why "non-working"? AFAIU, Emacs on X uses the colors known to the X
server, and doesn't consult that file. That file is only consulted on
non-X platforms, such as MS-Windows. So using it would mean that
Emacs on MS-Windows will support colors that Emacs on X might not
support (if the X server doesn't). Do we really want that?
prev parent reply other threads:[~2023-10-17 11:10 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
2023-10-17 10:45 ` Po Lu
2023-10-17 11:10 ` Eli Zaretskii [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
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=83lec1o66n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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).