unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Randy Taylor <dev@rjt.dev>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: font-lock-delimiter-face - what for?
Date: Wed, 28 Dec 2022 17:13:49 +0200	[thread overview]
Message-ID: <328c8aa9-4a5d-218e-92d0-94ca27a709ca@yandex.ru> (raw)
In-Reply-To: <010a042a-cfd5-517b-cd2a-cb797c3390e5@yandex.ru>

On 27/12/2022 23:34, Dmitry Gutov wrote:
> On 27/12/2022 23:01, Stefan Monnier wrote:
>> Dmitry Gutov [2022-12-27 21:45:33] wrote:
>>> On 27/12/2022 20:20, Randy Taylor wrote:
>>>> font-lock-punctuation-face covers all punctuation.
>>>> The rest (bracket, delimiter, misc-punctuation) are for the more 
>>>> specific
>>>> kinds, with misc-punctuation being anything not a bracket or
>>>> delimiter. For example, see bash-ts-mode which specifies $ as
>>>> misc-punctuation.
>>> Oh... kay? So "misc punctuation" is punctuation which is not 
>>> punctuation?
>> IIUC `font-lock-punctuation-face` is a "parent face" for all forms of
>> punctuation, and then each actual punctuation is expected to use either
>> the delimiter, bracket, or misc face.
> 
> Ah. That would make sense.

Maybe it would be better to remove font-lock-misc-punctuation-face, though?

People can still use font-lock-punctuation-face for everything 
punctuation-like that doesn't match the category of "brackets" or 
"delimiters".

Just like font-lock-doc-face inherits from font-lock-string-face, or 
font-lock-comment-delimiter-face inherits from font-lock-comment-face.

We don't seem to have a practice of "parent faces" which are otherwise 
unused. font-lock-punctuation-face's docstring doesn't suggest this kind 
of purpose either.



  reply	other threads:[~2022-12-28 15:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27 15:44 font-lock-delimiter-face - what for? Dmitry Gutov
2022-12-27 16:44 ` Randy Taylor
2022-12-27 16:54   ` Dmitry Gutov
2022-12-27 18:20     ` Randy Taylor
2022-12-27 19:45       ` Dmitry Gutov
2022-12-27 21:01         ` Stefan Monnier
2022-12-27 21:34           ` Dmitry Gutov
2022-12-28 15:13             ` Dmitry Gutov [this message]
2022-12-28 17:06               ` Randy Taylor
2022-12-28 18:32                 ` Dmitry Gutov
2022-12-29  3:46                   ` Randy Taylor
2022-12-29 15:57                     ` Dmitry Gutov
2022-12-29 18:41                       ` Randy Taylor
2022-12-30  4:59                         ` Yuan Fu
2022-12-27 17:00 ` Eli Zaretskii
2022-12-27 19:46   ` Dmitry Gutov

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=328c8aa9-4a5d-218e-92d0-94ca27a709ca@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=dev@rjt.dev \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).