From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Must filladapt be disabled? (Was: Filladapt's "fill-paragraph" during "W w")
Date: 21 Dec 1999 09:24:25 -0500 [thread overview]
Message-ID: <ltiu1sbcdi.fsf@asfast.com> (raw)
In-Reply-To: Per Abrahamsen's message of "21 Dec 1999 10:53:14 +0100"
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Hrvoje Niksic <hniksic@iskon.hr> writes:
>
> > Hrvoje Niksic <hniksic@iskon.hr> writes:
> >
> > > > : > : > > here is a very long line. here is a very long line. here is a...
> > > > : > : > > here is a very long line. here is a very long line. here is a...
> >
> > I've just noticed that gnus-cite doesn't handle this either. Oh well.
>
> It does if you have two of them. The gnus-cite heuristics wants at
> least two quoted lines, or a quoted line and an attribution line, in
> order to recognize something as a citation prefix. Otherwise, it gets
> too many false positives.
Well, my goal is for `fill-paragraph' (`M-q') and other `fill-*'
commands to work the same was as `gnus-cite-*' ... or vice versa :)
If its not desirable for `gnus-cite-*' to use filladapt during
`fill-region', how about there being a way for `fill-paragraph' and
its cousins to use the algorithms in `gnus-cite'?
I'd just like my paragraphs and citations to be filled in a consistent
manner.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1999-12-21 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-18 16:53 Reformatting multi-level quotes Anders Melchiorsen
1999-12-18 21:53 ` Hrvoje Niksic
1999-12-18 22:51 ` Filladapt's "fill-paragraph" during "W w" (Was: Reformatting multi-level quotes) Lloyd Zusman
1999-12-18 23:04 ` Hrvoje Niksic
1999-12-18 23:20 ` Lloyd Zusman
1999-12-21 1:15 ` Must filladapt be disabled? (Was: Filladapt's "fill-paragraph" during "W w") Lloyd Zusman
1999-12-21 8:08 ` Hrvoje Niksic
1999-12-21 8:17 ` Hrvoje Niksic
1999-12-21 9:53 ` Per Abrahamsen
1999-12-21 14:24 ` Lloyd Zusman [this message]
1999-12-21 16:25 ` Lloyd Zusman
2000-04-21 17:20 ` Lars Magne Ingebrigtsen
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=ltiu1sbcdi.fsf@asfast.com \
--to=ljz@asfast.com \
/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.
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 NNTP newsgroup(s).