From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: [PATCH 0/2] two minor fixes for new/empty nnimap group handling
Date: Thu, 09 Jul 2015 09:47:16 -0400 [thread overview]
Message-ID: <87mvz5xx23.fsf@uwo.ca> (raw)
In-Reply-To: <87r3oixctn.fsf@uwo.ca>
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)
next prev parent reply other threads:[~2015-07-09 13:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 11:37 Bjørn Mork
2015-07-01 11:37 ` [PATCH 1/2] nnimap.el (nnimap-request-group): don't make nil into a list Bjørn Mork
2015-07-01 11:37 ` [PATCH 2/2] nnimap.el (nnimap-request-group): group could be empty Bjørn Mork
2015-07-01 11:50 ` [PATCH 0/2] two minor fixes for new/empty nnimap group handling Alan Schmitt
2015-07-01 12:23 ` Bjørn Mork
2015-07-01 13:49 ` Alan Schmitt
2015-07-02 2:18 ` Nikolaus Rath
2015-07-06 2:45 ` Eric Abrahamsen
2015-07-06 8:40 ` Bjørn Mork
2015-07-06 15:11 ` Eric Abrahamsen
2015-07-06 15:32 ` Dan Christensen
2015-07-07 2:48 ` Eric Abrahamsen
2015-07-07 23:12 ` Dan Christensen
2015-07-08 4:20 ` Eric Abrahamsen
2015-07-08 21:45 ` Dan Christensen
2015-07-09 1:53 ` Eric Abrahamsen
2015-07-09 2:52 ` Dan Christensen
2015-07-09 13:47 ` Dan Christensen [this message]
2015-07-10 2:41 ` Eric Abrahamsen
2015-07-10 12:42 ` Dan Christensen
2015-07-12 4:11 ` Eric Abrahamsen
2015-07-12 4:27 ` Eric Abrahamsen
2015-07-12 17:01 ` Dan Christensen
2015-07-13 5:36 ` Eric Abrahamsen
2015-07-08 12:41 ` Eric Abrahamsen
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=87mvz5xx23.fsf@uwo.ca \
--to=jdc@uwo.ca \
--cc=ding@gnus.org \
/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).