Gnus development mailing list
 help / color / mirror / Atom feed
From: Miles Bader <miles@gnu.org>
Subject: Re: Gnus vs Wanderlust
Date: Wed, 02 Jun 2004 07:35:54 +0900	[thread overview]
Message-ID: <87zn7mvrcl.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <vgvekoz46ef.wl@paias746.morganstanley.com>

colin.rafferty@morganstanley.com writes:
> I love Gnus as a news reader.  I use it actively, and think it is the
> best news reader ever.  However, the needs of a mail reader are
> different from a news reader.

I've always thought this was a very silly argument.  I also find that I
have slightly different preferences for mail and news, but the amount of
_shared_ behavior is _huge_.  It seems bizarre to say "Oh just implement
a completely new system!" instead of just fixing the problems with Gnus.
Not only is the amount of duplicated work enormous, but it's a burden
for the _user_ to have to learn and configure two separate systems,
especially once they start to explore more advanced features.

It's possible that the Gnus framework is so ill-suited to, say, caching
that this would be even more work, but it seems unlikely.

The main complaints I've seen about Gnus behavior with email are
(1) summary generation speed, and (2) lack of rmail-style `categories'.

I don't know much about (2), but with regards to (1), at least with
backends such as nnml -- which does cache summary information, if not
pre-formatted summaries -- the main problem I've had seems to be the
same that you mention:  it deals poorly with sparse article ranges.
Fixing this would go a _long_ way towards making it perfect for me.

-Miles
-- 
Freedom's just another word, for nothing left to lose   --Janis Joplin




  reply	other threads:[~2004-06-01 22:35 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 [this message]
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
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=87zn7mvrcl.fsf@tc-1-100.kawasaki.gol.ne.jp \
    --to=miles@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).