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: Mon, 18 Nov 2013 05:42:13 +0200 [thread overview]
Message-ID: <8361rqgyui.fsf@gnu.org> (raw)
In-Reply-To: <87a9h264do.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Drew Adams <drew.adams@oracle.com>, 15900@debbugs.gnu.org
> Date: Sun, 17 Nov 2013 23:38:11 +0100
>
> Hello,
>
> > > I think he means that the value of property `face' (whether from
> > > a text property or an overlay property) can be a list of faces.
>
> Indeed. Plus, I want to look at the font-lock-face property.
>
> > Yes, but then you get all that list in a single call to
> > get-char-property, right? So where's the difficulty in collecting
> > "all the faces at point"?
>
> There's no difficulty.
Then I don't understand why you still want to analyze colors instead
of analyzing faces. This is what my suggestion boiled down to:
instead of trying to figure out the foreground color of the text at
point, just compare its face(s) with a list of known faces whose
appearance you don't want to override.
> Eli, did you ever read the code snip I had included?
Of course, I did. But it still talks about colors, something I
suggested to avoid.
next prev parent reply other threads:[~2013-11-18 3:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#15900: 24.3.50; foreground-color-at-point returns wrong results 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 [this message]
2013-11-18 7:50 ` Michael Heerdegen
[not found] <<c18e0f8c-e172-497d-b572-69162d77132b@default>
[not found] ` <<83iovsgqhn.fsf@gnu.org>
2013-11-16 22:53 ` Drew Adams
[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
2013-11-15 2:04 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
2013-11-17 5:35 ` Michael Heerdegen
2013-11-17 17:21 ` Eli Zaretskii
2022-04-22 13:30 ` Lars Ingebrigtsen
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=8361rqgyui.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 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.