From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: furthermore! (nnimap splitting con't)
Date: Thu, 06 Mar 2014 13:00:09 +0800 [thread overview]
Message-ID: <87vbvrly5i.fsf@ericabrahamsen.net> (raw)
I swear I'm cursed, I'm the only person on this list who has ever had
imap splitting problems. If you search the archives for "imap split",
it's all me.
So now that I've made a little progress fixing splitting, I'm trying to
manually respool some of the mis-split articles into their proper
groups. `gnus-summary-respool-article' blows up with the backtrace
below.
The problem is that when gnus-summary-move-article calls
gnus-request-move-article, it passes along a nil "to-newsgroup"
parameter. Ie, it requests a move, but doesn't say where to move to.
From what I can tell, the problem is around gnus-sum.el:9962. There's a
branch that checks "(and (not to-newsgroup) (not select-method))", but
no branch that checks "(and (not to-newsgroup) select-method)", which
according to the docstring is where respooling would happen. I tried
changing the former to the latter, thinking that the
gnus-read-move-group-name call might do the spooling for me, but it just
prompted me for a group name, I guess because my gnus-move-split-methods
is nil. I'd never even heard of that variable. Should it be set to
something by default?
Anyway, I don't know if I'm the only person with this problem, or just
the only person trying to respool imap messages, but looking at the code
I just don't see how it would work...
Sadly,
Eri
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
decode-coding-string(nil utf-8)
nnimap-decode-gnus-group(nil)
nnimap-request-accept-article(nil "Girzel" t)
gnus-request-accept-article(nil (nnimap "Girzel" ETC) t t)
eval((gnus-request-accept-article nil (quote (nnimap "Girzel" ETC)) t t))
nnimap-request-move-article(103 "mail.misc" "Girzel" (gnus-request-accept-article nil (quote (nnimap "Girzel" ETC)) t t) t nil)
gnus-request-move-article(103 "nnimap+Girzel:mail.misc" "Girzel" (gnus-request-accept-article nil (quote (nnimap "Girzel" ETC)) t t) t nil)
gnus-summary-move-article(nil nil (nnimap "Girzel" ETC))
gnus-summary-respool-article(nil (nnimap "Girzel" ETC))
call-interactively(gnus-summary-respool-article nil nil)
next reply other threads:[~2014-03-06 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 5:00 Eric Abrahamsen [this message]
2014-03-06 9:12 ` Steinar Bang
2014-03-06 11:07 ` Eric Abrahamsen
2014-03-06 11:11 ` Rainer M Krug
2014-03-07 17:07 ` Lars Ingebrigtsen
2014-03-07 17:22 ` Lars Ingebrigtsen
2014-03-08 5:03 ` Eric Abrahamsen
2014-03-10 4:55 ` Eric Abrahamsen
2014-03-18 1:53 ` Eric Abrahamsen
2014-03-10 7:06 ` 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=87vbvrly5i.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).