Re: nnmaildir oddities!

[Simon Josefsson <jas@extundo.com>]

Josh Huber <huber+dated+1028145806.d34009@alum.wpi.edu> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> I didn't follow this thread closely, but respooling in Gnus used
>> either nnmail internal stuff or some undocumented backend interface,
>> which explains why it doesn't work for nnimap.  Maybe the same
>> applied to nnmaildir.  Documenting the backend interface for
>> respooling should be possible though, as well as fixing nnimap.el.
>> Anyone? :)
>
> Well, the problem in nnmaildir was that when you call the respool
> function (and eventually call nnmaildir-request-move-article, I
> think), it's called with a nil destination group value.  In nnml, this
> triggers a lookup with your split rules, with nnmaildir this triggers
> the backend to save in the current group. (i.e. where it came from)

Ah, yes, this was the undocumented backend interface I was talking
about.  Perhaps it should be mentioned in the manual that a nil group
means the backends' split stuff should place the article.  What about
the following?  Maybe nnimap will support it now that it is documented. :-)

--- gnus.texi.~6.294.~	2002-07-26 20:04:47.000000000 +0200
+++ gnus.texi	2002-07-26 22:31:48.000000000 +0200
@@ -23632,6 +23632,9 @@
 The function should return a cons where the @code{car} is the group name and
 the @code{cdr} is the article number that the article was entered as.
 
+If @var{group} is nil, it means the article is respooled and it should
+be placed in a group determined by the backends' split rules (if any).
+
 There should be no data returned.
 
> IMHO, the determination of the destination group should happen much
> earlier in the game -- doing in buried in each backend is just not the
> right thing to do.

Split rules are backend specific in Gnus.  But I agree, it would be
nicer if there was a `gnus-split-rules' that could crosspost across
backends too.