From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57087@debbugs.gnu.org, dalanicolai@gmail.com
Subject: bug#57087: 29.0.50; (face-at-point nil t) does not return all faces when hl-line-mode is active
Date: Wed, 10 Aug 2022 05:28:33 +0300 [thread overview]
Message-ID: <83lerwsuge.fsf@gnu.org> (raw)
In-Reply-To: <87a68dtdky.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 09 Aug 2022 21:35:25 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: dalanicolai <dalanicolai@gmail.com>, 57087@debbugs.gnu.org
> Date: Tue, 09 Aug 2022 21:35:25 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This is a misunderstanding of what the doc string means when it says
> > "faces". It doesn't mean that you should see more than one face in
> > the above situation.
> >
> > This is not a bug, it's just that your expectations from what
> > face-at-point can do are incorrect.
>
> Then I think this doc string needs clarification, at least:
Yes, probably. However, "return the first one" doesn't tell which one
this would be. Also "character has more than one face" is inaccurate,
we should say "more than one source of face information" or somesuch.
> I think it sounds like it would be more useful if it did indeed return
> all the faces at point instead of just the face(s) from either the
> overlay or the face(s) from the text property.
AFAICT, there's only one user of MULTIPLE, and that is org.el, so we
should ask them what they expect. There's always a possibility to add
a new function, say faces-at-point.
next prev parent reply other threads:[~2022-08-10 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 18:55 bug#57087: 29.0.50; (face-at-point nil t) does not return all faces when hl-line-mode is active dalanicolai
2022-08-09 19:20 ` Eli Zaretskii
2022-08-09 19:35 ` Lars Ingebrigtsen
2022-08-10 2:28 ` Eli Zaretskii [this message]
2022-08-12 13:55 ` 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
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=83lerwsuge.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57087@debbugs.gnu.org \
--cc=dalanicolai@gmail.com \
--cc=larsi@gnus.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).