From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29456@debbugs.gnu.org, tom@tromey.com,
"Simen Heggestøyl" <simenheg@gmail.com>,
monnier@iro.umontreal.ca
Subject: bug#29456: [PATCH] Add command for cycling between CSS color formats
Date: Mon, 27 Nov 2017 10:41:29 -0700 [thread overview]
Message-ID: <87a7z7aaba.fsf@tromey.com> (raw)
In-Reply-To: <83indv645v.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 Nov 2017 19:07:56 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> The latter follows the X color definitions, so why does css-mode.el
Eli> need a different interpretation of the hex-RGB notation?
CSS color names came from X a long time ago, but their mapping to rgb is
now part of the CSS specification. And, apparently there were multiple
versions of this file coming from X. The Emacs one would be ok provided
the lists are identical and will always remain so. Otherwise, css-mode
needs its own list.
Eli> My fear is that someone will mix css-mode functions with those from
Eli> elsewhere in Emacs, and will bump into confusing and contradicting
Eli> results. Is it possible to avoid that?
Using "css-" in the name seems sufficient to me. Maybe a comment
explaining this would help as well.
Tom
next prev parent reply other threads:[~2017-11-27 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 15:21 bug#29456: [PATCH] Add command for cycling between CSS color formats Simen Heggestøyl
2017-11-26 17:53 ` Tom Tromey
2017-11-27 17:07 ` Eli Zaretskii
2017-11-27 17:41 ` Tom Tromey [this message]
2017-11-27 18:11 ` Eli Zaretskii
2017-11-27 18:35 ` Tom Tromey
2017-11-27 18:43 ` Eli Zaretskii
2017-11-28 18:33 ` Simen Heggestøyl
2017-11-28 20:57 ` Simen Heggestøyl
2017-12-10 12:46 ` Simen Heggestøyl
2017-12-10 18:09 ` Eli Zaretskii
2017-12-17 9:32 ` Simen Heggestøyl
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=87a7z7aaba.fsf@tromey.com \
--to=tom@tromey.com \
--cc=29456@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=simenheg@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.