From: Keith David Bershatsky <esq@lawlist.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22757@debbugs.gnu.org
Subject: bug#22757: 25.1.50; `face-at-point` and `faces--attribute-at-point` -- add argument WINDOW-OR-BUFFER
Date: Mon, 22 Feb 2016 10:17:04 -0800 [thread overview]
Message-ID: <m2ziusk3tr.wl%esq@lawlist.com> (raw)
In-Reply-To: <m2egc67xci.wl%esq@lawlist.com>
Sorry, the last email had an automatically generated subject line that I use in my personal setup. Here is a fixed subject line.
I agree that `get-char-property` is the key ingredient, and it would be prudent to steer users to that function. It does, however, require an advanced level of Lisp expertise to understand how to use it to achieve certain goals. I probably wouldn't have been able to figure out (in a reasonable period of time) how to get foreground/background at point without standing on the shoulders of others -- e.g., `foreground-color-at-point` and `background-color-at-point`.
Keith
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
At Mon, 22 Feb 2016 17:58:13 +0200,
Eli Zaretskii wrote:
>
>
> Sorry, I don't think I follow. I asked whether calling
> get-char-property directly, instead of going through face-at-point,
> would have done the job you needed to do. I still think it would
> have, even after reading your response.
>
> My point is that I see no particular reason why users should try using
> face-at-point in this situation. That function is not documented in
> the ELisp manual, whereas get-char-property is. So I'm not sure why
> we should consider adding an argument to face-at-point to support use
> cases that seem to be already supported by get-char-property. Can you
> clarify this aspect?
>
> Thanks.
next prev parent reply other threads:[~2016-02-22 18:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 18:05 bug#22757: 25.1.50; `face-at-point` and `faces--attribute-at-point` -- add argument WINDOW-OR-BUFFER Keith David Bershatsky
2016-02-21 20:54 ` Eli Zaretskii
2016-02-21 21:23 ` Keith David Bershatsky
2016-02-22 15:58 ` Eli Zaretskii
2016-02-21 21:23 ` Keith David Bershatsky
2016-02-22 18:15 ` bug#22757: Reply to correspondence dated February 22, 2016 Keith David Bershatsky
2016-02-22 19:25 ` Eli Zaretskii
2022-02-03 20:51 ` bug#22757: 25.1.50; `face-at-point` and `faces--attribute-at-point` -- add argument WINDOW-OR-BUFFER Lars Ingebrigtsen
2016-02-22 18:17 ` Keith David Bershatsky [this message]
2016-02-22 19:46 ` Keith David Bershatsky
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=m2ziusk3tr.wl%esq@lawlist.com \
--to=esq@lawlist.com \
--cc=22757@debbugs.gnu.org \
--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).