From: dsg@linus.mitre.org (David S. Goldberg)
Subject: Hiding overly long To and CC headers
Date: 04 Sep 1997 09:43:30 -0400 [thread overview]
Message-ID: <m1bk9gxurct.fsf@blackbird.mitre.org> (raw)
Unfortunately too many people here rely on personal mailing lists for
things like all department mailings rather than using lists set up by
the corporation. If they'd use the latter, the To or CC header would
show up with the list name. Since they use the former, recipients
have to page through several dozens of lines of To or CC header to
(finally!) read a much smaller message. I often find my self typing
">" and a couple of "b"'s (which I've bound to gnus-summary-prev-page)
if necessary to get by it quickly, but WIBN if there was a way to
easily wash the To and CC headers or, more generically, all continued
header lines. Perhaps continued lines could be considered a boring
condition?
--
Dave Goldberg
Post: The Mitre Corporation\MS B305\202 Burlington Rd.\Bedford, MA 01730
Phone: 617-271-3887
Email: dsg@mitre.org
next reply other threads:[~1997-09-04 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-04 13:43 David S. Goldberg [this message]
1997-09-08 10:53 ` 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=m1bk9gxurct.fsf@blackbird.mitre.org \
--to=dsg@linus.mitre.org \
--cc=dsg@mitre.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).