From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: custom-set-faces for various file types
Date: Sun, 22 Nov 2020 22:16:45 +0100 [thread overview]
Message-ID: <trinity-5997ab05-d677-436e-9ceb-313a8d8580fa-1606079805896@3c-app-mailcom-bs01> (raw)
In-Reply-To: <87sg91cdpd.fsf@web.de>
> Sent: Sunday, November 22, 2020 at 9:57 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: custom-set-faces for various file types
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > I am setting custom-set-faces for various file types (e.g. .org).
> > I see that emacs requires only one instance of custom-set-variables.
> >
> > When setting custom-set-faces for org mode, is it acceptable to put
> > the custom-set-faces code for that file type in the corresponding
> > org-init.el file (etc for other file types).
> >
> > Or is it a better strategy in have all custom-set-faces together?
>
> 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 can call it once in emacs-init.el, then call custom-set-faces
in each major mode init file where I would like a change.
Another possibility is to put them all together in emacs-init.el that
sets the highlighting, even though I would also have separate
org-init.el, texi-init.el, and so on.
> Michael.
next prev parent reply other threads:[~2020-11-22 21:16 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 [this message]
2020-11-22 21:39 ` Michael Heerdegen
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=trinity-5997ab05-d677-436e-9ceb-313a8d8580fa-1606079805896@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).