Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: ding@gnus.org
Subject: Re: Just shoot me now
Date: Wed, 22 Dec 2010 17:54:00 +0100	[thread overview]
Message-ID: <0hlj3hwxxz.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m2wrn14vo6.fsf@verilab.com> (Tommy Kelly's message of "Wed, 22 Dec 2010 10:30:33 -0600")

Tommy Kelly <tommy.kelly@verilab.com> writes:

> Sivaram Neelakantan <nsivaram.net@gmail.com> writes:
>> Funnily, mail splitting worked for me the first time I tried apart
>> from a few minor misses.  But mine were simple ones
>>
>> (setq nnmail-split-methods
>>       '(("sas-l" "^Subject:.*SAS-L*")
>> ;; 	("ctan-ann" "^From:.*ctan-ann*")
>>  	("mail.misc" "")))
>>
>> is all I did.
>
> Ah but see that's simple splitting. That's for girls (cue slaps for
> sexism and threats to get Sacha Chua to kick my ass). Real Men use
> *fancy* splitting.  And it's fancy splitting that's destroying my will
> to live. :-)
>
>> WhyTF, I didn't
>> understand it the first time around or for that matter many other
>> times before, I don't know.
>
> Exactly right. It's normal, once you become more expert to forget what
> it was like to be a newb.
>
> But a key component of writing good docs, much as in good teaching, is
> precisely the ability to rewind your mind to that first time around,
> remember what it was like to not know what you now know, and to plot a
> path forwards for the newbie. 
>
> Most people find that hard. The few that can are called good
> teachers. The very best of those are called Richard Feynman.
>
>> Of course, the fault is mostly mine that I make feeble attempts at
>> learning elisp....
>
> Well yes and no. To me it's not unreasonable that if you want to get to
> grips with the dark underbelly of Gnus (or anything in emacs) you have
> to roll your sleeves up and dig into lisp. But that doesn't mean the
> documentation is fine.
>
> Again -- lest Lars, Andreas and the other Noble Writers Of Code get fed
> up with what may seem like whining, just keep hacking guys. You are much 
> appreciated. 
>
> Tommy

Abd just in case anyone is reading this, I still havent got an example
of fancy splitting working, Here is my setup:-

,----
|    (setq spam-use-bogofilter t)
|    (setq spam-use-spamassassin t)
|    
|    (require 'spam)
|    (spam-initialize)
|    
|    (setq nnimap-split-inbox '("INBOX"))
|    (setq nnimap-split-fancy '(| (: spam-split) "INBOX"))
| 
|    (setq nnmail-split-inbox '("INBOX"))
|    (setq nnmail-split-fancy '(| (: spam-split) "SYS-INBOX"))
|    
|    (setq spam-split-disabled nil)
|    
|    (setq spam-autodetect-recheck-messages nil)
|    (setq spam-mark-ham-unread-before-move-from-spam-group t)
|    (setq spam-mark-new-messages-in-spam-group-as-spam t)
|    (setq spam-split-group "Gnus-Spam")
`----
   
And no splitting is happening on the INBOX. I cant think what else might
be inhibiting it so if no one can help I'll try, gulp, to debug it...




  reply	other threads:[~2010-12-22 16:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 22:29 What's wrong with this fancy split? Tommy Kelly
2010-12-21 22:41 ` Andreas Schwab
2010-12-21 23:50   ` Russ Allbery
2010-12-22  0:17     ` Tommy Kelly
2010-12-22  9:32     ` Andreas Schwab
2010-12-22 10:16       ` Steinar Bang
2010-12-22 10:28         ` Andreas Schwab
2010-12-22 10:35           ` Steinar Bang
2010-12-22 10:44             ` Andreas Schwab
2010-12-22 11:44               ` Bjørn Mork
2010-12-22 12:26               ` Tommy Kelly
2010-12-22 12:37                 ` Tassilo Horn
2010-12-22 12:59                   ` Tommy Kelly
2010-12-22 13:48                     ` Steinar Bang
2010-12-22 16:10                       ` Tommy Kelly
2010-12-22 17:46                         ` Steinar Bang
2010-12-22 18:19                           ` Tommy Kelly
2010-12-22 19:15                             ` Steinar Bang
2010-12-22 19:53                               ` Tommy Kelly
2010-12-22 22:12                                 ` Steinar Bang
2010-12-22 23:31                                   ` Tommy Kelly
2010-12-23 19:05                                     ` Steinar Bang
2010-12-22 15:39               ` Richard Riley
2010-12-22 12:34           ` Tommy Kelly
2010-12-22  0:13   ` Just shoot me now (was Re: What's wrong with this fancy split?) Tommy Kelly
2010-12-22  7:24     ` Just shoot me now Reiner Steib
2010-12-22 13:57       ` Richard Riley
2010-12-22 14:18         ` Tommy Kelly
2010-12-22 15:54           ` Sivaram Neelakantan
2010-12-22 16:30             ` Tommy Kelly
2010-12-22 16:54               ` Richard Riley [this message]
2010-12-22 17:12                 ` Tommy Kelly
2010-12-22 17:14                 ` Lawrence Mitchell
2010-12-22 17:43                   ` Richard Riley
2010-12-22 18:07                   ` Tommy Kelly
2010-12-22 22:40                   ` Richard Riley
2010-12-22 19:25           ` Eric S Fraga
2010-12-22  7:26     ` Just shoot me now (was Re: What's wrong with this fancy split?) Richard Riley
2010-12-22  9:35     ` Andreas Schwab
2010-12-22 12:53       ` Tommy Kelly
2010-12-22 18:21         ` Adam Sjøgren
2010-12-22 19:12           ` Tommy Kelly
2010-12-22 19:44             ` Adam Sjøgren

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=0hlj3hwxxz.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.org \
    --cc=tommy.kelly@verilab.com \
    /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).