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

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Dan Christensen <jdc@uwo.ca> writes:

> I forgot that I was running a wrapper around nnmairix-search that hid an
> error it commonly produced.  This might explain the strange behaviour
> we've been seeing.  In the past, things worked fine if I ignored this
> error and just tried again to enter the group, but with the changes
> to nnimap.el in the past six months, that is no longer the case.
>
> Dan
>
> Debugger entered--Lisp error: (error "Group nnmairix+mairixserver:nnmairixsearch couldn't be activated ")
>   signal(error ("Group nnmairix+mairixserver:nnmairixsearch couldn't be activated "))
>   error("Group %s couldn't be activated " "nnmairix+mairixserver:nnmairixsearch")
>   gnus-list-of-unread-articles("nnmairix+mairixserver:nnmairixsearch")
>   gnus-select-newsgroup("nnmairix+mairixserver:nnmairixsearch" t nil)
>   gnus-summary-read-group-1("nnmairix+mairixserver:nnmairixsearch" t t nil nil nil)
>   gnus-summary-read-group("nnmairix+mairixserver:nnmairixsearch" t t nil nil nil nil)
>   gnus-group-read-group(nil t "nnmairix+mairixserver:nnmairixsearch")
>   nnmairix-search("test d:1w-")
>   call-interactively(nnmairix-search record nil)
>   command-execute(nnmairix-search record)
>   execute-extended-command(nil "nnmairix-search")
>   call-interactively(execute-extended-command nil nil)

Yeah, I think in the end nnmairix will probably have to be adjusted --
it's fallen behind in several regards, and my guess is it's just not
quite doing the right thing anymore.

Just so I'm perfectly clear: the above error is what you get without
running *any* of the patches I or Bjørn have sent, and with your wrapper
removed? Just plain vanilla Gnus?

Eric