From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 15900@debbugs.gnu.org
Subject: bug#15900: 24.3.50; foreground-color-at-point returns wrong results
Date: Sun, 17 Nov 2013 05:52:33 +0200 [thread overview]
Message-ID: <83eh6fhegu.fsf@gnu.org> (raw)
In-Reply-To: <87siuv21v8.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 15900@debbugs.gnu.org, drew.adams@oracle.com
> Date: Sun, 17 Nov 2013 03:33:47 +0100
>
> > > If faces are among them, I still must figure out if one of these
> > > faces changes the foreground.
> >
> > You can know them in advance, I think. Your example talks about
> > links, which use a known face. I presume there are only a few faces
> > that needs such a special treatment, which would make the list of them
> > quite short.
> >
> > IOW, why not test against a known list of properties that you want to
> > leave alone, instead of digging into their color?
>
> I think the missing information you didn't have is that this is a
> general mode, it must work in any Emacs buffer. w3m was only an example
> - info, man, and gnus are others. So, testing for hardcoded face or
> property lists is not really an option.
I still don't see why it isn't an option, even for a general-purpose
mode. The list of faces that need such special treatment must be
quite short, and it can be a defcustom.
next prev parent reply other threads:[~2013-11-17 3:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 2:04 bug#15900: 24.3.50; foreground-color-at-point returns wrong results Michael Heerdegen
2013-11-15 2:47 ` Michael Heerdegen
2013-11-15 8:26 ` Eli Zaretskii
2013-11-15 22:18 ` Michael Heerdegen
2013-11-16 0:26 ` Drew Adams
2013-11-16 8:57 ` Eli Zaretskii
2013-11-16 8:44 ` Eli Zaretskii
2013-11-17 2:33 ` Michael Heerdegen
2013-11-17 3:52 ` Eli Zaretskii [this message]
2013-11-17 5:35 ` Michael Heerdegen
2013-11-17 17:21 ` Eli Zaretskii
2022-04-22 13:30 ` Lars Ingebrigtsen
[not found] <<87siuyxvw7.fsf@web.de>
[not found] ` <<83li0qhxyl.fsf@gnu.org>
[not found] ` <<878uwpgvh8.fsf@web.de>
[not found] ` <<b0006d1c-b470-4297-a6d7-97d7ed118c28@default>
[not found] ` <<83vbzshggy.fsf@gnu.org>
2013-11-16 16:20 ` Drew Adams
2013-11-16 16:40 ` Eli Zaretskii
[not found] ` <<83y54ohh1n.fsf@gnu.org>
[not found] ` <<87siuv21v8.fsf@web.de>
[not found] ` <<83eh6fhegu.fsf@gnu.org>
[not found] ` <<87eh6flhfc.fsf@web.de>
[not found] ` <<83d2lzgd04.fsf@gnu.org>
2013-11-17 17:29 ` Drew Adams
2013-11-17 17:47 ` Eli Zaretskii
2013-11-17 22:38 ` Michael Heerdegen
2013-11-18 3:42 ` Eli Zaretskii
2013-11-18 7:50 ` Michael Heerdegen
[not found] <<6bc49739-fae0-4688-a3cc-8bbbc2fe1c04@default>
[not found] ` <<83li0ogv14.fsf@gnu.org>
2013-11-16 17:47 ` Drew Adams
2013-11-16 18:18 ` Eli Zaretskii
[not found] <<c18e0f8c-e172-497d-b572-69162d77132b@default>
[not found] ` <<83iovsgqhn.fsf@gnu.org>
2013-11-16 22:53 ` Drew Adams
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=83eh6fhegu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15900@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).