unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jostein@kjonigsen.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: bat-mode: Inconsistent fontification. Consider using font-lock-function-name-face
Date: Tue, 10 Sep 2019 21:49:02 +0200	[thread overview]
Message-ID: <87imq02aq9.fsf@gmx.de> (raw)
In-Reply-To: <83v9u010q8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Sep 2019 21:10:23 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> The moment new faces are added I expect users to start complaining
> that these faces are not supported by this and that foo-mode.  So mode
> authors aren't forced to implement them only in theory, IMO.

For modes in elpa, there is also the backward compatibility problem. So
they cannot feel forced to apply such new faces directly.

Asking for similar faces for similar syntactic entities in different
modes is legitimate. IMHO.

These new faces give mode authors a hint how to provide own customized
faces as long as necessary. And moving to the new faces will happen over
the years only.

Best regards, Michael.



  reply	other threads:[~2019-09-10 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-09  8:49 bat-mode: Inconsistent fontification. Consider using font-lock-function-name-face Jostein Kjønigsen
2019-09-09 10:48 ` Andy Moreton
2019-09-09 16:09   ` Eli Zaretskii
2019-09-09 17:34     ` Jostein Kjønigsen
2019-09-09 18:10       ` Eli Zaretskii
2019-09-09 19:26         ` Jostein Kjønigsen
2019-09-09 20:32           ` Clément Pit-Claudel
2019-09-09 21:41 ` Stefan Monnier
2019-09-10  4:29   ` Jostein Kjønigsen
2019-09-10 12:48     ` Stefan Monnier
2019-09-10 14:54     ` Eli Zaretskii
2019-09-10 16:56       ` Jostein Kjønigsen
2019-09-10 18:10         ` Eli Zaretskii
2019-09-10 19:49           ` Michael Albinus [this message]
2019-09-18 19:21             ` Jostein Kjønigsen

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=87imq02aq9.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --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).