From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: fill-column is misused in *Article*
Date: 03 Dec 1998 13:27:11 -0500 [thread overview]
Message-ID: <86ww49rshs.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "03 Dec 1998 12:53:06 -0500"
Karl Kleinpaste <karl@justresearch.com> writes:
> After rendering text/html segments, fill-column seems to be left behind
> in the setting in which it was used for HTML rendering, which means that
> it is wrong when the next garden variety text/plain article comes along
> whose lines are too long and which I therefore want to reformat with `W
> w'. It would be good if either HTML rendering were not to mess with the
> value already present in *Article*, or if the default fill-column were
> re-asserted just before the article is presented (before W3 changes it
> again, that is, so that it's the normal setting for other types of
> articles).
I suppose gnus could do a:
(let ((fill-column fill-column))
... w3 render ...
)
-bp
prev parent reply other threads:[~1998-12-03 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-03 17:53 Karl Kleinpaste
1998-12-03 18:27 ` William M. Perry [this message]
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=86ww49rshs.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.com \
--cc=ding@gnus.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.
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).