From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Folding long header lines
Date: Sun, 30 Dec 2001 02:20:58 +0100 [thread overview]
Message-ID: <m3n101jyf9.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <yl1yhdo854.fsf@windlord.stanford.edu>
Russ Allbery <rra@stanford.edu> writes:
> Which seems to argue in favor of either 1) or 4). (Personally, I'd rather
> see headers folded for display than see headers wrap because they're over
> 80 columns; folded headers are easier to read.)
Yup. I've made the unfolding function only unfold if the result is
less wide than the window you're using.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-12-30 1:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 22:06 Lars Magne Ingebrigtsen
2001-12-29 22:50 ` Jesper Harder
2001-12-29 23:16 ` Lars Magne Ingebrigtsen
2001-12-30 0:37 ` Russ Allbery
2001-12-30 1:20 ` Lars Magne Ingebrigtsen [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=m3n101jyf9.fsf@quimbies.gnus.org \
--to=larsi@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).