From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: larsi@gnus.org, 50041@debbugs.gnu.org
Subject: bug#50041: Add font-lock-doc-markup-face
Date: Fri, 13 Aug 2021 17:12:50 +0300 [thread overview]
Message-ID: <8335rdcu1p.fsf@gnu.org> (raw)
In-Reply-To: <1A815899-9854-4042-B4C1-BCF85BF4E794@acm.org> (message from Mattias Engdegård on Fri, 13 Aug 2021 16:08:59 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 13 Aug 2021 16:08:59 +0200
> Cc: 50041@debbugs.gnu.org
>
> > Which one of these justifies having these faces in font-lock.el, as
> > opposed in markdown mode itself, or in rst.el?
>
> All of them -- it's not primarily intended for editing whole texts in those formats (and modes) but for doc comments specific to each programming language. Fontifying those is done by the respective language mode, such as haskell-mode or java-mode.
>
> Sorry if I was unclear on that point. I've made the NEWS entry a bit less ambiguous.
>
> > It is unusual to have
> > mode-specific faces in a general-purpose Lisp file, let alone a
> > preloaded one.
>
> The face is not mode-specific. It's like font-lock-doc-face.
Sorry, I still don't get it. Could you show a couple of examples of
use of this face, and tell how these use cases are handled without
that face? TIA.
next prev parent reply other threads:[~2021-08-13 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 10:53 bug#50041: Add font-lock-doc-markup-face Mattias Engdegård
2021-08-13 12:15 ` Lars Ingebrigtsen
2021-08-13 13:08 ` Eli Zaretskii
2021-08-13 14:08 ` Mattias Engdegård
2021-08-13 14:12 ` Eli Zaretskii [this message]
2021-08-13 14:34 ` Mattias Engdegård
2021-08-13 15:57 ` Eli Zaretskii
2021-08-13 17:41 ` Mattias Engdegård
2021-08-13 18:31 ` Eli Zaretskii
2021-08-13 21:24 ` Mattias Engdegård
2021-08-14 5:56 ` Eli Zaretskii
2021-08-14 9:01 ` Mattias Engdegård
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=8335rdcu1p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50041@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
/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).