From: Stefan Monnier <email@example.com>
To: "Vincent Belaïche" <firstname.lastname@example.org>
Cc: Org mode <email@example.com>, firstname.lastname@example.org
Subject: Re: Alinea filling (hanlding of explicit line-breaks)
Date: Wed, 16 Feb 2011 10:02:37 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> ("Vincent =?iso-8859-1?Q?Bela=EFch?= =?iso-8859-1?Q?e=22's?= message of "Wed, 16 Feb 2011 07:42:31 +0100")
>> An important question here is: is it important for M-} to ignore those \\?
> I guess so, this is the current default Org behaviour anyhow.
> as far as I understand, it would be anyhow possible to move point on
> an alinea-by-alinea basis just by configuring the tailing \\ as
> anohter paragraph separator.
Actually, no, because paragraph-separate would cause the whole line that
ends with \\ to be treated as not being part of a paragraph, and
paragraph-start wouldn't be appropriate either.
Hence the "good" above :-(
>> Of course fill-paragraph-function sucks because it only applies to
>> fill-paragraph and not to fill-region.
> Do you mean that `fill-paragraph-function' is some kind of obsolete
> feature and that people should use another kind of hook, and if so
> which one?
Yes and no: there is no replacement for it. There is
fill-forward-paragraph-function, which can handle some of the cases for
which fill-paragraph-function has been used, but there would need to be
something like a fill-region-as-paragraph-function and we don't have
that yet :-(
next prev parent reply other threads:[~2011-02-16 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 6:42 Alinea filling (hanlding of explicit line-breaks) Vincent Belaïche
2011-02-16 15:02 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-13 15:48 Alinea filling (hanlding of explicit line-breaks) Vincent Belaïche
2011-03-13 21:34 ` Stefan Monnier
2011-03-13 13:49 Alinea filling (hanlding of explicit line-breaks) Vincent Belaïche
2011-03-12 21:09 Vincent Belaïche
2011-03-13 3:59 ` Stefan Monnier
2011-02-14 21:30 Vincent Belaïche
2011-02-15 17:22 ` Stefan Monnier
2011-02-13 8:47 Vincent Belaïche
2011-02-14 18:16 ` Stefan Monnier
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).