From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, 49558@debbugs.gnu.org, lisa-asket@perso.be
Subject: bug#49558: fill paragraph in texinfo-mode fails with @
Date: Wed, 14 Jul 2021 16:29:43 +0200 [thread overview]
Message-ID: <87v95dhstk.fsf@gnus.org> (raw)
In-Reply-To: <83y2a96lb6.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 14 Jul 2021 17:07:25 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> But even if we do so, I'm not sure that
>
> @cindex relative remapping, faces
> @cindex base remapping, faces
> The following functions implement a higher-level interface to
> @code{face-remapping-alist}. Most Lisp code should use these
> functions instead of setting @code{face-remapping-alist} directly, to
> avoid trampling on remappings applied elsewhere. These functions are
> intended for buffer-local remappings, so they all make
> @code{face-remapping-alist} buffer-local as a side-effect. They manage
> @code{face-remapping-alist} entries of the form
>
> should be a single paragraph,
But it is one paragraph today. With my proposed patch, it becomes two
paragraphs (since @cindex is the start of a paragraph).
> and likewise this:
>
> @defun face-remap-add-relative face &rest specs
> This function adds the face spec in @var{specs} as relative
> remappings for face @var{face} in the current buffer. The remaining
> arguments, @var{specs}, should form either a list of face names, or a
> property list of attribute/value pairs.
There would be no difference here -- that's one paragraph both before
and after the patch.
My preference would be to have the first example be three paragraphs,
and the second example two paragraphs, but I have no idea how to make
that happen with any paragraph-start/separate settings.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-07-14 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 3:57 bug#49558: fill paragraph in texinfo-mode fails with @ lisa-asket
2021-07-14 7:47 ` Lars Ingebrigtsen
2021-07-14 12:01 ` Eli Zaretskii
2021-07-14 12:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-14 13:11 ` Eli Zaretskii
2021-07-14 13:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-14 14:03 ` Eli Zaretskii
2021-07-14 13:00 ` Lars Ingebrigtsen
2021-07-14 13:13 ` Eli Zaretskii
2021-07-14 13:15 ` Lars Ingebrigtsen
2021-07-14 13:22 ` Eli Zaretskii
2021-07-14 13:53 ` Lars Ingebrigtsen
2021-07-14 14:07 ` Eli Zaretskii
2021-07-14 14:29 ` Lars Ingebrigtsen [this message]
2021-11-07 22:58 ` Lars Ingebrigtsen
2021-07-14 13:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87v95dhstk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=49558@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lisa-asket@perso.be \
--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).