unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: 29456@debbugs.gnu.org, simenheg@gmail.com, monnier@iro.umontreal.ca
Subject: bug#29456: [PATCH] Add command for cycling between CSS color formats
Date: Mon, 27 Nov 2017 20:11:21 +0200	[thread overview]
Message-ID: <83d1436186.fsf@gnu.org> (raw)
In-Reply-To: <87a7z7aaba.fsf@tromey.com> (message from Tom Tromey on Mon, 27 Nov 2017 10:41:29 -0700)

> From: Tom Tromey <tom@tromey.com>
> Cc: Simen Heggestøyl <simenheg@gmail.com>,
>   29456@debbugs.gnu.org,  tom@tromey.com,  monnier@iro.umontreal.ca
> Date: Mon, 27 Nov 2017 10:41:29 -0700
> 
> >>>>> "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.

Sorry, I don't understand: what list are you talking about?

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

A comment will help, but I'm actually wondering why does css-mode need
to use 12-bit or 16-bit per component RGB notation?  Why not use only
8-bit, as in #RRGGBB?  The problems only happen in converting 8-bit
RGB notations to higher number of bits.





  reply	other threads:[~2017-11-27 18:11 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
2017-11-27 18:11     ` Eli Zaretskii [this message]
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

  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=83d1436186.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29456@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=simenheg@gmail.com \
    --cc=tom@tromey.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).