From: Tim Cross <tcross@nospam.une.edu.au>
Subject: Re: face at point
Date: 18 Nov 2002 09:40:28 +1100 [thread overview]
Message-ID: <87vg2v6crn.fsf@blind-bat.une.edu.au> (raw)
In-Reply-To: m2bs4reg1l.fsf@mother.paradise.lost
John Hunter <jdhunter@nitace.bsd.uchicago.edu> writes:
> [ I recently inadvertently posted this to g.e.gnus, but it really
> belongs here. Sorry for the crosspost ]
>
> I don't really understand how to identify what faces are in use in a
> given buffer.
>
I find the following two functions very useful
,----[ C-h f list-colors-display RET ]
| list-colors-display is an interactive compiled Lisp function in `facemenu'.
| (list-colors-display &optional LIST)
|
| Display names of defined colors, and show what they look like.
| If the optional argument LIST is non-nil, it should be a list of
| colors to display. Otherwise, this command computes a list
| of colors that the current display can handle.
`----
and
,----[ C-h f list-text-properties-at RET ]
| list-text-properties-at is an interactive compiled Lisp function in `facemenu'.
| (list-text-properties-at P)
|
| Pop up a buffer listing text-properties at LOCATION.
`----
As I also find many of the "default colours don't work well with a
dark background, I usually start my customization of emacs colours by
setting the default foreground/background and then using
list-colors-display to see the values for all loaded faces and setting
those which are difficult to read. If I find there is still a face in
some mode which is difficult to read I put the cursor on a bit of the
text and use list-text-properties-at-point to identify which face i
need to set.
Tim
next prev parent reply other threads:[~2002-11-17 22:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 2:13 face at point John Hunter
2002-11-15 2:50 ` Jesper Harder
2002-11-15 3:30 ` John Hunter
2002-11-15 3:40 ` Jesper Harder
2002-11-15 10:24 ` Oliver Scholz
2002-11-15 13:37 ` Jesper Harder
2002-11-15 14:51 ` Jesper Harder
2002-11-15 16:58 ` Oliver Scholz
2002-11-16 18:49 ` Kai Großjohann
2002-11-15 4:24 ` Miles Bader
[not found] ` <mailman.1037335988.3983.help-gnu-emacs@gnu.org>
2002-11-15 14:21 ` Michael J Downes
2002-11-15 14:31 ` John Hunter
2002-11-17 22:40 ` Tim Cross [this message]
2002-11-17 23:00 ` Miles Bader
2002-11-18 5:54 ` Tim Cross
2002-11-18 8:52 ` Miles Bader
[not found] ` <mailman.1037610573.27378.help-gnu-emacs@gnu.org>
2002-11-18 13:48 ` Fredrik Staxeng
2002-11-18 17:23 ` Oliver Scholz
2002-11-18 18:16 ` Fredrik Staxeng
2002-11-18 17:56 ` Eli Zaretskii
[not found] ` <mailman.1037646827.31512.help-gnu-emacs@gnu.org>
2002-11-19 6:02 ` Fredrik Staxeng
2002-11-19 6:47 ` Eli Zaretskii
2002-11-19 9:20 ` Miles Bader
2002-11-19 20:24 ` Kai Großjohann
2002-11-18 22:06 ` Tim Cross
2002-11-18 22:36 ` Jesper Harder
2002-11-19 2:00 ` Miles Bader
2002-11-19 1:55 ` Miles Bader
2002-11-19 5:31 ` Eli Zaretskii
[not found] ` <mailman.1037671096.385.help-gnu-emacs@gnu.org>
2002-11-19 5:58 ` Tim Cross
2002-11-19 6:24 ` Eli Zaretskii
2002-11-19 6:24 ` Fredrik Staxeng
2002-11-19 6:56 ` Eli Zaretskii
2002-11-19 8:56 ` Miles Bader
[not found] ` <mailman.1037696237.22239.help-gnu-emacs@gnu.org>
2002-11-19 9:46 ` Fredrik Staxeng
[not found] <mailman.1037688495.14173.help-gnu-emacs@gnu.org>
2002-11-19 8:54 ` Fredrik Staxeng
2002-11-19 18:14 ` Eli Zaretskii
[not found] ` <mailman.1037733383.18353.help-gnu-emacs@gnu.org>
2002-11-20 13:37 ` Fredrik Staxeng
2002-11-20 16:13 ` Eli Zaretskii
[not found] ` <mailman.1037812462.4160.help-gnu-emacs@gnu.org>
2002-11-20 17:56 ` Fredrik Staxeng
[not found] <mailman.1037687132.614.help-gnu-emacs@gnu.org>
2002-11-19 22:16 ` Tim Cross
2002-11-20 5:47 ` Eli Zaretskii
2002-11-20 11:06 ` Oliver Scholz
2002-11-20 14:01 ` Stefan Monnier <foo@acm.com>
2002-11-20 16:00 ` Michael Slass
[not found] <mailman.1037771296.12946.help-gnu-emacs@gnu.org>
2002-11-20 7:34 ` Miles Bader
2002-11-20 7:39 ` Kai Großjohann
[not found] ` <mailman.1037777785.20916.help-gnu-emacs@gnu.org>
2002-11-20 11:10 ` Oliver Scholz
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=87vg2v6crn.fsf@blind-bat.une.edu.au \
--to=tcross@nospam.une.edu.au \
/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.