From: Lloyd Zusman <ljz@asfast.com>
Subject: Must filladapt be disabled? (Was: Filladapt's "fill-paragraph" during "W w")
Date: 20 Dec 1999 20:15:19 -0500 [thread overview]
Message-ID: <lt66xtccwo.fsf_-_@asfast.com> (raw)
In-Reply-To: Lloyd Zusman's message of "18 Dec 1999 18:20:33 -0500"
I'm replying to my own message because I've been investigating the issue
I brought up, and now I have a new question ...
Lloyd Zusman <ljz@asfast.com> writes:
> Hrvoje Niksic <hniksic@iskon.hr> writes:
>
> > Lloyd Zusman <ljz@asfast.com> writes:
> >
> > > [ ... ] what's the canonical method for causing filladapt's
> > > `fill-paragraph' function to be the one to run for each
> > > paragraph during the standard `W w' article washing procedure
> > > (`gnus-article-fill-cited-article')?
> >
> > I'm not sure you can do that at all. AFAIK gnus-cite implements its
> > own algorithms for filling articles. Ones that work quite well, so
> > I've never tried to replace them with filladapt.
>
> [ ... at this point, I originally said that
> `gnus-article-fill-cited-article' in `gnus-cite.el' was
> handling this correctly when `filladapt' was loaded, but I was
> mistaken ... ]
It turns out after all that `gnus-article-fill-cited-article' does
indeed disable `filladapt' processing. Look at the line with the
`***HERE***' comment in this excerpt of the function:
(defun gnus-article-fill-cited-article (&optional force width)
"Do word wrapping in the current article.
If WIDTH (the numerical prefix), use that text width when filling."
(interactive (list t current-prefix-arg))
(save-excursion
(set-buffer gnus-article-buffer)
(let ((buffer-read-only nil)
(inhibit-point-motion-hooks t)
(marks (gnus-dissect-cited-text))
(adaptive-fill-mode nil)
(filladapt-mode nil) ;; ***HERE***
(fill-column (if width (prefix-numeric-value width) fill-column)))
(save-restriction
;;; etc. ...
By turning `filladapt-mode' off, the standard `fill-region' gets
called and not the one that would have been overridden by the
`filladapt' version.
Is there any compelling reason for `filladapt-mode' to be turned off
here? If not, could this line just get removed (and possibly the line
above with `adaptive-fill-mode' also)? Or if it's important to
usually turn this off, could this then be controlled by some special
variable, maybe sort of like this??? ...
(filladapt-mode (if gnus-cite-use-filladapt filladapt-mode))
... where `gnus-cite-use-filladapt' is a variable whose default value
is `nil' but which could be optionally customized to be `t'.
This way, people like me could force `filladapt' filling during
article washing.
Any thoughts?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1999-12-21 1:15 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 ` Lloyd Zusman [this message]
1999-12-21 8:08 ` Must filladapt be disabled? (Was: Filladapt's "fill-paragraph" during "W w") Hrvoje Niksic
1999-12-21 8:17 ` Hrvoje Niksic
1999-12-21 9:53 ` Per Abrahamsen
1999-12-21 14:24 ` Lloyd Zusman
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=lt66xtccwo.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).