From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: custom-set-faces for various file types
Date: Sun, 22 Nov 2020 22:39:08 +0100 [thread overview]
Message-ID: <87im9xcbr7.fsf@web.de> (raw)
In-Reply-To: trinity-5997ab05-d677-436e-9ceb-313a8d8580fa-1606079805896@3c-app-mailcom-bs01
Christopher Dimech <dimech@gmx.com> writes:
> > What is your goal? Faces looking differently depending on the major
> > mode?
>
> I would like that some special constructs are highligthed so that the
> contrast would be suitable for assistive reasons. For instance, in
> current texinfo modes, constructs in pure tex do not get highlighted.
> So I have some code that uses custom-set-faces in texi-init.el.
>
> The Manual says that custom-set-variables must be only called once.
> [...]
I don't think custom is the right tool for your purpose. Face
definitions are global. You can switch between settings ("themes"), but
the effect is always global.
For texinfo, maybe you could instead change the font-locking of the
mode? It's defined in `texinfo-font-lock-keywords'. Maybe it's enough
to add an entry to that list?
Emacs also supports per-buffer modifications of faces. The mechanism is
called "face-remap". You could use it in the mode's hooks to change how
a face looks like in buffers using that mode. `face-remap-add-relative'
is the function to use, takes a face and a list of specs. Using that
would be a cleaner solution for your case I think.
Michael.
next prev parent reply other threads:[~2020-11-22 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 17:30 custom-set-faces for various file types Christopher Dimech
2020-11-22 20:57 ` Michael Heerdegen
2020-11-22 21:16 ` Christopher Dimech
2020-11-22 21:39 ` Michael Heerdegen [this message]
2020-11-22 22:04 ` Christopher Dimech
2020-11-22 22:10 ` Christopher Dimech
2020-11-22 22:53 ` Christopher Dimech
2020-11-22 23:38 ` Michael Heerdegen
2020-11-22 23:52 ` Christopher Dimech
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=87im9xcbr7.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).