Re: split-fancy-with-parent

[Ted Zlatanov]

On Wed, 23 Mar 2011 18:36:46 +0100 Vincent Beffara <vbeffara@ens-lyon.fr> 
wrote: 

VB> Aha. So I did this:

VB> ,----
VB> | (setq gnus-select-method '(nnimap "local"
VB> |                               (nnimap-address "localhost")
VB> |                               (nnimap-stream network)
VB> |                               (nnimap-inbox "INBOX")
VB> |                               (nnimap-split-methods 'nnimap-split-fancy)
VB> |                               (nnimap-split-fancy
VB> |                                (| (: 
gnus-registry-split-fancy-with-parent)
VB> |                                   "INBOX"))
VB> |                               ))
VB> `----

VB> and everything works great. That is fantastic, thanks a lot !

I'm glad.

VB> If I understand correctly, this will only split messages arriving in
VB> INBOX ? Is there a way I can split all incoming messages in all
VB> mailboxes, but setting the default rule to "wherever the message was
VB> delivered" rather than always INBOX ?

I don't think so, currently.  But you could write a group-entry function
(there's a hook for those) that looks at the unseen messages, runs
`gnus-registry-split-fancy-with-parent' on each one, and moves them to
the return value if it's a string (group name).  I would gladly put that
in gnus-registry.el so everyone can benefit from it.

VB> PS: BTW, now "B t" to test where a message would end up consistenty
VB> answers "mail.misc" even on a message that was correctly split. And
VB> respooling with "B r" fails saying

VB> wrong type argument: stringp, nil

VB> But I can live with that.

I haven't looked at that code in a loooong time.  Could you do
`M-x toggle-debug-on-error', generate the wrong type error, and post the
backtrace, to be sure it's not something local to you?

Thanks
Ted