From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15668-done@debbugs.gnu.org,
"darren.hoo@gmail.com Hoo" <darren.hoo@gmail.com>
Subject: bug#15668: 24.3.50; No font lock on active region
Date: Fri, 1 Nov 2013 16:54:46 +0100 [thread overview]
Message-ID: <7D46A066-4DCB-45DE-8815-34E60FC58260@swipnet.se> (raw)
In-Reply-To: <83eh7djmn4.fsf@gnu.org>
Hello.
22 okt 2013 kl. 18:28 skrev Eli Zaretskii <eliz@gnu.org>:
>> From: Jan Djärv <jan.h.d@swipnet.se>
>> Date: Tue, 22 Oct 2013 18:14:03 +0200
>> Cc: darren.hoo@gmail.com,
>> 15668@debbugs.gnu.org
>>
>> Hello.
>>
>> 21 okt 2013 kl. 21:06 skrev Eli Zaretskii <eliz@gnu.org>:
>>
>>>> From: Jan Djärv <jan.h.d@swipnet.se>
>>>> Date: Mon, 21 Oct 2013 20:47:25 +0200
>>>> Cc: Darren Hoo <darren.hoo@gmail.com>,
>>>> 15668@debbugs.gnu.org
>>>>
>>>> It would be nice if one could define a face with a foreground color to be used when foreground and background otherwise are to similar.
>>>
>>> Sounds like a simple enough extension to defface.
>>
>> Well, yes, but I envisioned that querying the face for the foreground would automatically give the "fallback" foreground when the background is close to the foreground that would otherwise be used.
>
> That's what I had in mind, yes.
>
>> I think the calculation of close and maybe handling face inheritance is a bit tricky.
>
> Some distance in the RGB space might fit the former. I'm quite sure
> color comparison is something for which algorithms are readily
> available.
Actually there is a color_distance function in xfaces.c already.
I implemented :distant-foreground to be used as a fallback, checked in to trunk.
Marking this bug as done.
Jan D.
next prev parent reply other threads:[~2013-11-01 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 5:56 bug#15668: 24.3.50; No font lock on active region Darren Hoo
2013-10-21 16:30 ` Eli Zaretskii
2013-10-21 18:47 ` Jan Djärv
2013-10-21 19:06 ` Eli Zaretskii
2013-10-21 19:20 ` Eli Zaretskii
2013-10-22 16:14 ` Jan Djärv
2013-10-22 16:28 ` Eli Zaretskii
2013-11-01 15:54 ` Jan Djärv [this message]
2013-10-21 21:36 ` Darren Hoo
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=7D46A066-4DCB-45DE-8815-34E60FC58260@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15668-done@debbugs.gnu.org \
--cc=darren.hoo@gmail.com \
--cc=eliz@gnu.org \
/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).