From: Alan Shutko <ats@acm.org>
Subject: Re: text/plain format="filled" issue (or bug?)
Date: 10 Aug 2000 16:22:57 -0400 [thread overview]
Message-ID: <m3hf8srhlq.fsf@wesley.springies.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "10 Aug 2000 22:02:39 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Are anybody here familiar with the bowels of `fill-region', which is
> what flow-fill uses? Does it set `fill-column' under some conditions?
I don't know, but I just noticed that W3 sets it buffer-local if
you view a text/html message, and it'll last as long as the
*Article* buffer isn't deleted.
Yes, that's it (for me, at least). flow-fill is _not_ resetting
fill-column, but if you view an HTML message before hand, it will
get reset and flow-fill will use that value.
--
Alan Shutko <ats@acm.org> - In a variety of flavors!
92 days, 19 hours, 17 minutes, 15 seconds till we run away.
You recoil from the crude; you tend naturally toward the exquisite.
next prev parent reply other threads:[~2000-08-10 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 3:28 Daniel Pittman
2000-08-10 20:02 ` Lars Magne Ingebrigtsen
2000-08-10 20:22 ` Alan Shutko [this message]
2000-08-10 20:42 ` 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=m3hf8srhlq.fsf@wesley.springies.com \
--to=ats@acm.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).