From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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:22:31 +0300 [thread overview]
Message-ID: <831r8181yg.fsf@gnu.org> (raw)
In-Reply-To: <87k0ltjauf.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 14 Jul 2021 15:15:04 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: monnier@iro.umontreal.ca, lisa-asket@perso.be, 49558@debbugs.gnu.org
> Date: Wed, 14 Jul 2021 15:15:04 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> > @node Foo Bar Baz Quux Very Long Node Name
> >> >
> >> > @subsection This is a very long subsection name
> >> >
> >> > @cindex a very long index entry that could wrap
> >> >
> >> > @defun my-func with many different arguments that could wrap
> >> >
> >> > @end multitable
> >>
> >> The problem is that all of that is currently a single paragraph -- and I
> >> don't think that's something we want? (Try saying
> >> `M-: (forward-paragraph)' at the start.)
> >
> > What exactly do we not want in the result of forward-paragraph in
> > these cases? I'm probably missing something.
>
> I think the example text you pasted should be five paragraphs, not one.
That's because you think about it as plain text. It isn't.
Basically, lines that start with @foo are directives, not text.
It could be somewhat surprising, because it otherwise looks very much
like plain text, but without those definitions of paragraph-start and
paragraph-separate, things would be much worse. E.g., copy this to a
text-mode buffer, then type M-q:
@itemize @bullet
@item
If the text consists of a special glyph, the glyph can specify a
particular face. @xref{Glyphs}.
next prev parent reply other threads:[~2021-07-14 13:22 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 [this message]
2021-07-14 13:53 ` Lars Ingebrigtsen
2021-07-14 14:07 ` Eli Zaretskii
2021-07-14 14:29 ` Lars Ingebrigtsen
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=831r8181yg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49558@debbugs.gnu.org \
--cc=larsi@gnus.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).