Re: [PATCH 0/2] two minor fixes for new/empty nnimap group handling

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Bjørn Mork <bjorn@mork.no> writes:

> The recent nnimap speedups introduced a couple of regressions wrt
> new and empty nnimap groups. This prevents Gnus from creating new
> IMAP groups.
>
> These two patches fix the problems for me, but are created in the
> way I usually do lisp: by mindless trial and error until emacs
> stops complaining. I.e., there might be much better ways to fix
> this...
>
> Anyway: Works For Me (tm)
>
>
> Bjørn Mork (2):
>   nnimap.el (nnimap-request-group): don't make nil into a list
>   nnimap.el (nnimap-request-group): group could be empty
>
>  lisp/nnimap.el | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)

Hi Bjørn,

I'm guessing you only see this when you move a message from one group
into a non-existent group, and you're prompted to create the new group,
and it gives you an error. Is that right?

The group actually is created, it just gives an error when it's
re-selected. That's because the move/copy process doesn't automatically
subscribe to the group and register it with Gnus: if you go into the
*Server* buffer and open the group list for the server in question,
you'll see the new group there, unsubscribed.

My feeling is that groups which are created as part of the article
move/copy process should be automatically subscribed to, and registered
with Gnus (ie entered into gnus-newsrc-hashtb). That would solve this
problem, and also seems like the Right Thing to Do.

Does anyone have any opinions on this? I'll work up a patch, if not.

Eric