[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15900: 24.3.50; foreground-color-at-point returns wrong results
From: |
Michael Heerdegen |
Subject: |
bug#15900: 24.3.50; foreground-color-at-point returns wrong results |
Date: |
Sun, 17 Nov 2013 06:35:03 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> > > 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.
>From the user's point of view, yes, it's an option. But you mentioned
it saying it would be easier to realize in Lisp. This is what I have:
(cl-some
(lambda (face) (not (memq (face-foreground face nil t)
`(nil
,(face-attribute 'default :foreground)
"unspecified-fg" "unspecified-bg"))))
(cl-mapcan (lambda (face-or-list) (if (facep face-or-list)
(list face-or-list)
face-or-list))
(list
(get-text-property (point) 'face)
(get-text-property (point) 'font-lock-face))))
For your solution, I can use a different predicate, but would still have
to find all faces at point, no? What do I miss?
Regards,
Michael.
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, (continued)
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Drew Adams, 2013/11/15
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Drew Adams, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Drew Adams, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Drew Adams, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Michael Heerdegen, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/16
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results,
Michael Heerdegen <=
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/17
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Drew Adams, 2013/11/17
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/17
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Michael Heerdegen, 2013/11/17
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Eli Zaretskii, 2013/11/17
- bug#15900: 24.3.50; foreground-color-at-point returns wrong results, Michael Heerdegen, 2013/11/18