all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29456@debbugs.gnu.org, Tom Tromey <tom@tromey.com>,
	simenheg@gmail.com, monnier@iro.umontreal.ca
Subject: bug#29456: [PATCH] Add command for cycling between CSS color formats
Date: Mon, 27 Nov 2017 11:35:04 -0700	[thread overview]
Message-ID: <87609va7tz.fsf@tromey.com> (raw)
In-Reply-To: <83d1436186.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 27 Nov 2017 20:11:21 +0200")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

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

Sorry, I misunderstood.

CSS also specifies hex and rgb syntax itself.

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

#RGB is specified by CSS, it is equivalent to #RRGGBB, and is often
seen.  With css-color-4, #RGBA is also allowed.

Basically css-mode needs to understand the peculiarities of CSS syntax,
which differs somewhat from other systems AFAIK.

Tom





  reply	other threads:[~2017-11-27 18:35 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
2017-11-27 18:35       ` Tom Tromey [this message]
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=87609va7tz.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.