From: Gijs Hillenius <gijs@hillenius.net>
To: ding@gnus.org
Subject: No Gnus v0.11: splitting, error: encode-coding-string(nil utf-7-imap)
Date: Mon, 25 Oct 2010 09:17:55 +0200 [thread overview]
Message-ID: <87k4l6ivvg.fsf@hillenius.net> (raw)
This is with No Gnus v0.11 gotten (gitted?) on October 19th,
Just now noticed that five messages in the INBOX did not get splitted to
their INBOX.folders. I use splitting with a hook to bbdb like so
,----
| (setq nnimap-split-fancy
| '(| (: gnus-folder-per-bbdb)
| ("From" "googlealerts.*" "INBOX.google-alerts")
| and more lines like the above
`----
Marking the unsplitted messages and hitting 'B r' asks me:
Backend to use when respooling (default nnimap):
Now, this value 'nnimap' is correct, but hitting tab here ^ prints [no
match]. And if I hit 'enter' (thus telling it to use the nnimap backend)
I get this error:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
encode-coding-string(nil utf-7-imap)
utf7-encode(nil t)
nnimap-request-accept-article(nil "thuis" t)
gnus-request-accept-article(nil (nnimap "thuis" (nnimap-address
"server") (nnimap-inbox "INBOX") (nnimap-split-methods
nnmail-split-fancy) (nnir-search-engine imap) (nnimap-stream ssl)) t
t)
gnus-summary-move-article(nil nil (nnimap "thuis" (nnimap-address
"server") (nnimap-inbox "INBOX") (nnimap-split-methods
nnmail-split-fancy) (nnir-search-engine imap) (nnimap-stream ssl))
copy)
gnus-summary-copy-article(nil nil (nnimap "thuis" (nnimap-address
"server") (nnimap-inbox "INBOX") (nnimap-split-methods
nnmail-split-fancy) (nnir-search-engine imap) (nnimap-stream ssl)))
gnus-summary-respool-article(nil (nnimap "thuis" (nnimap-address
"server") (nnimap-inbox "INBOX") (nnimap-split-methods
nnmail-split-fancy) (nnir-search-engine imap) (nnimap-stream ssl)))
call-interactively(gnus-summary-respool-article nil nil)
next reply other threads:[~2010-10-25 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 7:17 Gijs Hillenius [this message]
2010-10-29 22:23 ` Lars Magne Ingebrigtsen
2010-11-01 14:33 ` Gijs Hillenius
2010-11-01 18:46 ` Lars Magne Ingebrigtsen
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=87k4l6ivvg.fsf@hillenius.net \
--to=gijs@hillenius.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).