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: Sat, 14 Aug 2021 08:56:47 +0300 [thread overview]
Message-ID: <83r1ewbmcg.fsf@gnu.org> (raw)
In-Reply-To: <9A060FF9-242D-47DE-AA4D-D41BFA5779EE@acm.org> (message from Mattias Engdegård on Fri, 13 Aug 2021 23:24:13 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Fri, 13 Aug 2021 23:24:13 +0200
> Cc: larsi@gnus.org, 50041@debbugs.gnu.org
>
> > "Font Lock mode face used to highlight documentation."
>
> All faces have very terse doc strings and I naturally assumed that was the preferred style; it certainly didn't prevent me from understanding it. Anyway, I have amended the doc strings of both font-lock-doc-face and font-lock-doc-markup-face.
>
> > Also, I think "for mark-up elements" is too terse and assumes too much
> > of prior knowledge; we should make more clear what that means, or
> > provide a couple of examples.
>
> Maybe, but let's not exaggerate; this is standard terminology. Nevertheless, the text has been extended.
>
> > The NEWS entry is now clear enough, but I think the manual
> > and the doc string still need some work.
>
> Very well, they have now all been expanded further.
Thanks, this LGTM.
next prev parent reply other threads:[~2021-08-14 5:56 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1ewbmcg.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 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.