unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: goncholden <goncholden@protonmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: face-remap-add-relative versus set-face-attribute
Date: Sun, 13 Feb 2022 02:30:47 +0000	[thread overview]
Message-ID: <F1F0amVGqO8GGcdO8P_F_SlNYOHLXb4YsroZu3TOrw4JzDwUBJVk-kqeVxFosq4GjvtIXtp1pnlRluMh0Thk7biVgHVxO73LFfYSp2FATEY=@protonmail.com> (raw)
In-Reply-To: <8735kncxn3.fsf@zoho.eu>

------- Original Message -------
On Sunday, February 13th, 2022 at 2:23 AM, Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> goncholden wrote:
>
> > Would one prefer buffer local for customising comments?
>
> In general, no, since comments are a wide concept ...

Then with "(set-face-attribute" the comment customisation could be enough.  Ne need to go through the "(face-remap-add-relative" path.

> > > Don't forget about font-lock-comment-delimiter-face BTW ...
> >
> > What is its use?
>
> M-x describe-face RET font-lock-comment-delimiter-face RET
>
> -------------------------------------------------------------
>
> underground experts united
>
> https://dataswamp.org/~incal



  reply	other threads:[~2022-02-13  2:30 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 [this message]
2022-02-13  2:26     ` goncholden
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='F1F0amVGqO8GGcdO8P_F_SlNYOHLXb4YsroZu3TOrw4JzDwUBJVk-kqeVxFosq4GjvtIXtp1pnlRluMh0Thk7biVgHVxO73LFfYSp2FATEY=@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).