From: Tassilo Horn <tsdh@gnu.org>
To: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Subject: Re: fill-paragraph ill designed
Date: Wed, 26 Aug 2015 19:03:07 +0200 [thread overview]
Message-ID: <14f6af66db8.27bc.69bc538c4644581689883e654f15bce0@gnu.org> (raw)
In-Reply-To: <55DDED47.8080700@online.de>
No, I can't point at it. I spoke in the subjunctive, i.e., IMO it would be
the right thing to do for fill-region but currently it works differently.
On August 26, 2015 18:46:23 Andreas Röhler <andreas.roehler@online.de> wrote:
>
> Am 26.08.2015 um 14:40 schrieb Tassilo Horn:
>> Andreas Röhler <andreas.roehler@online.de> writes:
>>
>>>>>> There is a lot of ugliness in the way fill-paragraph works, but
>>>>>> developing a replacement that works ok in practice is harder than it
>>>>>> looks. I recall a time that we tried.
>>>>> What would prevent switching the clauses as suggested?
>>>> IMO, it makes completely sense that `fill-paragraph' delegates to
>>>> `fill-region' if the region is active so that not every mode-specific
>>>> `fill-paragraph-function' has to do that on its own.
>>> Let's assume region is up to or inside a documentation-string in
>>> Python.
>>>
>>> Then fill-region will be called instead of fill-paragraph-function.
>>>
>>> But how should fill-region get access or know about Python docu-string
>>> styles?
>> `fill-region' would utilize `fill-forward-paragraph-function' to move
>> over the paragraphs in that region
>
> okay
>
>> and call `fill-paragraph-function' on
>> them.
>
> Can't see that. May you point me at?
>
> Cheers,
>
> Andreas
>
>
next prev parent reply other threads:[~2015-08-26 17:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 8:24 fill-paragraph ill designed Andreas Röhler
2015-08-25 9:05 ` Tassilo Horn
2015-08-25 9:50 ` Andreas Röhler
2015-08-25 12:18 ` Tassilo Horn
2015-08-25 14:53 ` Stefan Monnier
2015-08-26 7:15 ` Tassilo Horn
2015-08-25 14:51 ` Stefan Monnier
2015-08-25 22:14 ` Richard Stallman
2015-08-26 6:30 ` Andreas Röhler
2015-08-26 7:08 ` Tassilo Horn
2015-08-26 12:22 ` Andreas Röhler
2015-08-26 12:40 ` Tassilo Horn
2015-08-26 16:45 ` Andreas Röhler
2015-08-26 17:03 ` Tassilo Horn [this message]
2015-08-27 16:35 ` Stefan Monnier
2015-08-27 17:48 ` Andreas Röhler
2015-08-28 6:30 ` Tassilo Horn
2015-08-28 6:41 ` Andreas Röhler
2015-08-28 8:26 ` Tassilo Horn
2015-08-29 19:47 ` Andreas Röhler
2015-08-30 7:30 ` Andreas Röhler
2015-08-31 1:21 ` Stefan Monnier
2015-08-28 16:27 ` Stefan Monnier
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=14f6af66db8.27bc.69bc538c4644581689883e654f15bce0@gnu.org \
--to=tsdh@gnu.org \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@gnu.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).