From: goncholden <goncholden@protonmail.com>
To: goncholden <goncholden@protonmail.com>
Cc: Emanuel Berg <moasenwood@zoho.eu>, help-gnu-emacs@gnu.org
Subject: Re: face-remap-add-relative versus set-face-attribute
Date: Sun, 13 Feb 2022 02:26:00 +0000 [thread overview]
Message-ID: <rbgTY9DpqeRJ5HSPTz-u3td99Z3vsg-fYyYFGjbgJ42bwFOjzUWoDy6MwXuwtOXGhmT3BiN2b4tGPxlYiPAaTdKe0cXZrXVGxTsGVvPXd_U=@protonmail.com> (raw)
In-Reply-To: <QsBUtaCAGqZML40SnJlx2OksY9gS1KkzARL-yd0pjQknqpoi1bKFGTMH-PP5bYVep2G-YEBon1TCEi8N8CK1Brt6In9intFsRNtBMJpSvNk=@protonmail.com>
------- Original Message -------
On Sunday, February 13th, 2022 at 2:12 AM, goncholden <goncholden@protonmail.com> wrote:
> ------- Original Message -------
> On Sunday, February 13th, 2022 at 12:59 AM, Emanuel Berg via Users list for the GNU Emacs text editor help-gnu-emacs@gnu.org wrote:
> > goncholden via Users list for the GNU Emacs text editor wrote:
> >
> > > What is superior? Using (face-remap-add-relative 'default :weight 'bold)
> > > or using (set-face-attribute 'font-lock-comment-face nil :weight normal) ?
> > They don't do the same thing ... But the second is good, except I don't
> > think one needs to `quote' font-lock-comment-face.
>
> face-remap-add-relative could be buffer local. Would one prefer buffer local for customising
> comments?
>
> > Don't forget about font-lock-comment-delimiter-face BTW ...
>
> > And try this ...
>
> > (defun set-all-faces (fg &optional bg weight)
> > (let ((backg (or bg "black"))
> > (wght (or weight 'normal))
> > (faces) )
> > (mapatoms (lambda (s)
> > (when (facep s)
> > (push (symbol-name s) faces) )))
> > (dolist (f faces)
> > (set-face-attribute (intern f) nil
> > :foreground fg)
> > :background backg
> > :weight wght
> > :italic nil) ))
>
> > (set-all-faces "red")
What is the use of set-all-faces, getting perplexed with it.
next prev parent reply other threads:[~2022-02-13 2:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 23:43 face-remap-add-relative versus set-face-attribute goncholden via Users list for the GNU Emacs text editor
2022-02-13 0:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 2:12 ` goncholden
2022-02-13 2:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 2:30 ` goncholden
2022-02-13 2:26 ` goncholden [this message]
2022-02-13 2:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 2:44 ` goncholden
2022-02-13 2:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 3:18 ` goncholden
2022-02-13 3:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 5:06 ` goncholden
2022-02-13 5:59 ` goncholden
2022-02-13 6:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 6:37 ` goncholden
2022-02-13 6:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 8:41 ` Jean Louis
2022-02-13 8:58 ` goncholden
2022-02-13 6:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 6:59 ` goncholden
2022-02-13 9:12 ` goncholden
2022-02-13 9:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-13 9:22 ` goncholden
2022-02-13 9:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
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='rbgTY9DpqeRJ5HSPTz-u3td99Z3vsg-fYyYFGjbgJ42bwFOjzUWoDy6MwXuwtOXGhmT3BiN2b4tGPxlYiPAaTdKe0cXZrXVGxTsGVvPXd_U=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).