From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: bat-mode: Inconsistent fontification. Consider using font-lock-function-name-face
Date: Tue, 10 Sep 2019 06:29:58 +0200 [thread overview]
Message-ID: <3668c95a-d8a0-1e31-c663-297ac684a8f1@secure.kjonigsen.net> (raw)
In-Reply-To: <jwv4l1ltahz.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
On 9/9/19 11:41 PM, Stefan Monnier wrote:
>
> FWIW, most modes distinguish function-definitions from
> function-references (aka function-calls), and I think that's a good
> thing (I like my definition to be highlighted in bold, but I like my
> function calls not to be highlighted at all).
>
>
> Stefan
>
Working mostly with OOP-related languages where functions can be
contained in both types -and- variables, I find the opposite is true for me.
Either way, isn't that a good argument to create dedicated font-lock
faces for those different uses, so that people with different
preferences can customize Emacs to their preferences?
For instance font-lock-function-name-face and font-lock-function-call-face ?
Again, are there any objectively negative or adverse side-effects of
adding more default-faces which authors can use and users can customize?
--
Vennlig hilsen
*Jostein Kjønigsen*
jostein@kjonigsen.net 🍵 jostein@gmail.com
https://jostein.kjønigsen.no
[-- Attachment #2: Type: text/html, Size: 2009 bytes --]
next prev parent reply other threads:[~2019-09-10 4:29 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 [this message]
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
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=3668c95a-d8a0-1e31-c663-297ac684a8f1@secure.kjonigsen.net \
--to=jostein@secure.kjonigsen.net \
--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).