From: Kevin Brubeck Unhammer <unhammer@fsfe.org>
To: info-gnus-english@gnu.org
Subject: wash forwarded threads
Date: Fri, 19 Mar 2021 09:40:58 +0100 [thread overview]
Message-ID: <87zgyz1qp1.fsf@trigram.no> (raw)
Hi,
I've read through the whole Info page on article washing, and now have
a much deeper appreciation for the dirty business of displaying readable
e-mails. However, there's a problem I still have: People keep forwarding
long threads of top-posted replies. Has anyone made anything to make
such things more readable? Ideally, it'd be possible to read such
e-mails as an ephemeral virtual group (similar to doing
`gnus-summary-enter-digest-group') where gnus has some heuristics for
looking for the next forwarded email, and splits the message into
a simple linear thread. Does this seem doable? Or has anyone else solved
this in some other way?
regards,
Kevin
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2021-03-19 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 8:40 Kevin Brubeck Unhammer [this message]
2021-03-28 18:37 ` nnimap-keepalive Bob Newell
2021-03-29 16:27 ` nnimap-keepalive Eric Abrahamsen
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=87zgyz1qp1.fsf@trigram.no \
--to=unhammer@fsfe.org \
--cc=info-gnus-english@gnu.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).