From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
"Ergus via Emacs development discussions." <emacs-devel@gnu.org>
Subject: Re: bat-mode: Inconsistent fontification. Consider using font-lock-function-name-face
Date: Tue, 10 Sep 2019 18:56:08 +0200 [thread overview]
Message-ID: <72cef0cb-d24b-4510-b73d-eced05d40bc0@www.fastmail.com> (raw)
In-Reply-To: <8336h42ocy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Tue, Sep 10, 2019, at 4:54 PM, Eli Zaretskii wrote:
> > From: Jostein Kjønigsen <jostein@secure.kjonigsen.net>
> > Date: Tue, 10 Sep 2019 06:29:58 +0200
> > Cc: emacs-devel@gnu.org
> >
> > Again, are there any objectively negative or adverse side-effects of adding more default-faces which authors
> > can use and users can customize?
>
> You mean, except requiring all the other major modes to implement it,
> including those outside the Emacs core? No other objections.
>
I don’t think that’s a fair way of putting it.
Giving major-mode authors more options with regard to faces they can use in their modes, does in no way -force- major-mode authors into using those if they don’t think they provide value.
Right now major-mode authors are already inventing their own non-standard font-lock-faces and giving them standard options to use instead can IMO only be considered an improvement.
[-- Attachment #2: Type: text/html, Size: 3566 bytes --]
next prev parent reply other threads:[~2019-09-10 16:56 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 [this message]
2019-09-10 18:10 ` Eli Zaretskii
2019-09-10 19:49 ` Michael Albinus
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=72cef0cb-d24b-4510-b73d-eced05d40bc0@www.fastmail.com \
--to=jostein@secure.kjonigsen.net \
--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).