Gnus development mailing list
 help / color / mirror / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: ding@gnus.org
Subject: Re: emacs 24 and gnus
Date: Sun, 09 Jan 2011 08:10:19 -0600	[thread overview]
Message-ID: <m28vyurwvo.fsf@verilab.com> (raw)
In-Reply-To: <c339p8x4lc.fsf@news.eternal-september.org>

Richard Riley <rileyrg@googlemail.com> writes:

> That is true, but I think I probably stick with the released Gnus at
> some point ( if I ever get my spam-split working again - I still havent
> see a working one with nnmail and nnimap split settings) as I had a few
> bad experiences with losing email in the last mad development phase
> which saw the brilliant IMAP improvements.

I concur. The excellent IMAP speed improvements aren't enough to
compensate for my inability to get fancy splitting working (although
that's not a new-versus-old-gnus issue -- just a
fancy-split-is-hard-to-get-working one). While I was spending time
wrestling with lisp, my email backlog grew to over 500 messages. And
then it grew further, to almost 1000, when at one point Gnus decided to
mark all my messages as read and I had no choice but to unmark enough
back in time so as to be sure I caught everything I hadn't yet handled!

Given that one of the reasons I moved to gnus was because of its support
for org-mode and org-mode itself is hard enough to learn, I'm
temporarily (I hope) having to revert to gmail via a browser (cue sound
of chicken clucking :-) ), at least until such times as I've gotten my
arms around org and can maybe have another crack at fancy splitting.

Tommy




  parent reply	other threads:[~2011-01-09 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 10:34 Richard Riley
2011-01-04 10:44 ` Tassilo Horn
2011-01-04 11:06   ` Richard Riley
2011-01-04 11:14     ` Adam Sjøgren
2011-01-04 11:58       ` Richard Riley
2011-01-04 12:04         ` Steinar Bang
2011-01-09 14:10         ` Tommy Kelly [this message]
2011-01-09 14:43           ` Richard Riley
2011-01-09 16:39             ` Tommy Kelly
2011-01-04 12:01     ` Tassilo Horn

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=m28vyurwvo.fsf@verilab.com \
    --to=tommy.kelly@verilab.com \
    --cc=ding@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).