From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: 22757@debbugs.gnu.org
Subject: bug#22757: Reply to correspondence dated February 22, 2016.
Date: Mon, 22 Feb 2016 21:25:44 +0200 [thread overview]
Message-ID: <83mvqsk0nb.fsf@gnu.org> (raw)
In-Reply-To: <m21t84ligw.wl%esq@lawlist.com> (message from Keith David Bershatsky on Mon, 22 Feb 2016 10:15:27 -0800)
> Date: Mon, 22 Feb 2016 10:15:27 -0800
> From: Keith David Bershatsky <esq@lawlist.com>
> Cc: 22757@debbugs.gnu.org
>
> 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`.
get-char-property gets you the face, and then face-foreground and
face-background (both documented in the ELisp manual) can be used to
get the colors.
next prev parent reply other threads:[~2016-02-22 19:25 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 [this message]
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
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=83mvqsk0nb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22757@debbugs.gnu.org \
--cc=esq@lawlist.com \
/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).