Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: Re: Gnus vs Wanderlust
Date: Wed, 02 Jun 2004 19:21:34 +0200	[thread overview]
Message-ID: <9eekoxho4h.fsf@fhi-berlin.mpg.de> (raw)
In-Reply-To: <vgvwu2q2d6m.wl-CC0PidyB7H7SDKTOTjYG+/RivMblJc010E9HWUfgJXw@public.gmane.org> (colin rafferty's message of "Wed, 02 Jun 2004 11:26:57 -0400")

Jumping in here only to give a somewhat different view. I still agree
that improved summary generation would be great.

On Wed, 02 Jun 2004 11:26:57 -0400 colin rafferty wrote:

colin> Both of these choices make a lot of sense for newsgroups, since in
colin> general, what was in the summary before has already been read, and the
colin> user won't be interested in it again.  However, with regular mail, you
colin> want to see everything, so it doesn't make sense.

I mainly use Gnus as a MUA and use it for that reason. I would be
perfectly happy to read the few newsgroups I look at using anything.

I have fairly large mail-groups with archived stuff that I always
never need. A typical group for me could contain 500 or 2500 messages,
most of which are "old". Then there might be 10, sometimes 50 ticked
articles I keep "visible" because they require a reaction at some
point or another. In addition there are of course often 1--50 new
messages when I enter a group. Overall there are typically 10--50
messages to be shown in the summary... Not so bad. (Especially not so
bad for my brain wading through a group. With the full list of
messages I would go mad.)

Then I wanna check an old email I now I stored. Normally it is obvious
what group it is in, so I might go there and simply ask for all
articles, then limit it to author or subject or search the messages --
this (i.e. opening with all messages) can be horribly slow, maybe also
because often message numbers are sparse; however, it doesn't happen
too often. So I can live with some delay here...

In the end hiding articles and that for me is "added functionality"
most MUAs don't provide.

Greetings,
Jochen
-- 
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
    Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
        (Part 3 you find in my messages before fall 2003.)




  parent reply	other threads:[~2004-06-02 17:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-31 10:22 Miguel
2004-05-31 23:03 ` Katsumi Yamaoka
2004-06-01 12:41   ` Lloyd Zusman
2004-06-01 14:40     ` Katsumi Yamaoka
2004-06-01 22:47       ` Lloyd Zusman
2004-06-02 12:33         ` David Abrahams
2004-06-01 15:58 ` colin.rafferty
2004-06-01 22:35   ` Miles Bader
2004-06-01 23:41     ` Katsumi Yamaoka
2004-06-02  0:13       ` Miles Bader
2004-06-02 15:26     ` colin.rafferty
     [not found]       ` <vgvwu2q2d6m.wl-CC0PidyB7H7SDKTOTjYG+/RivMblJc010E9HWUfgJXw@public.gmane.org>
2004-06-02 17:21         ` Jochen Küpper [this message]
2004-06-03 16:39       ` Kai Grossjohann
2004-06-03 19:28         ` colin.rafferty
     [not found]         ` <vgvwu2o1lwc.wl@paias746.morganstanley.com>
2004-06-04  5:16           ` Kai Grossjohann
2004-06-03 23:26       ` Miles Bader
2004-06-03 23:39         ` Lloyd Zusman
2004-06-04  0:05         ` Jesper Harder
2004-06-04  0:16           ` Miles Bader
2004-06-04  9:41         ` Simon Josefsson
2004-06-04 16:43           ` Karl Chen
2004-06-04 19:24             ` Kai Grossjohann
2004-06-05 10:40           ` Miles Bader
2004-06-05 15:14             ` Simon Josefsson
2004-06-06 18:35               ` Karl Chen
2004-06-06 20:31                 ` Simon Josefsson

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=9eekoxho4h.fsf@fhi-berlin.mpg.de \
    --to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).