From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: emacs-devel@gnu.org
Subject: Regarding adding additional default font-lock faces
Date: Wed, 01 Aug 2018 21:24:24 +0200 [thread overview]
Message-ID: <1533151464.4048871.1460317672.1FF86CD1@webmail.messagingengine.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hey everyone.
When considering expanding on things which gets fontified in typescript-
mode (a third-party major-mode), we noticed that some fairly common use-
cases don't have any appropriate font-lock-face variable to use, meaning
major-mode developers will have to make their own, one new defface for
each mode.
Examples of such use-cases and faces would be:
* function/method-call (that is invocation, not declaration)
* attributes/annotations for functions, classes, not to mention function-
parameters
I'm sure there are more, but those are at least some examples.
Not having a default font-face for this forces third-party packages
which rely on standard font-lock-faces for most values, to introduce
inconsistency by then suddenly creating some custom deffaces, which are
namespaced to their own package.
Add this up to several packages, and it can get messy. No theme will
certainly support this properly.
What does the emacs-community feel about expanding on the set of default
font-lock faces to include values for these? And how do we decided which
faces we should add?
--
Kind Regards
Jostein Kjønigsen
jostein@kjonigsen.net 🍵 jostein@gmail.com
https://jostein.kjonigsen.net
[-- Attachment #2: Type: text/html, Size: 2110 bytes --]
next reply other threads:[~2018-08-01 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 19:24 Jostein Kjønigsen [this message]
2018-08-01 21:53 ` Regarding adding additional default font-lock faces Stefan Monnier
2018-08-02 7:03 ` Jostein Kjønigsen
2018-08-02 11:53 ` Stefan Monnier
2018-08-03 7:46 ` Nathan Moreau
2018-08-09 11:04 ` Jostein Kjønigsen
2018-08-09 13:57 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1533151464.4048871.1460317672.1FF86CD1@webmail.messagingengine.com \
--to=jostein@secure.kjonigsen.net \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.