From: Joseph Gay <gilleylen@gmail.com>
To: ding@gnus.org
Subject: nnimap: possible bug with gnus-summary-move-article
Date: Wed, 06 Apr 2011 13:57:02 -0500 [thread overview]
Message-ID: <874o6bky2p.fsf@geneva.hpsy.me> (raw)
On No Gnus v0.16 --- sha1 04c1fb9
Previously I could move (B-m) a mail from a subscribed nnimap group to a
non-existent IMAP folder, and Gnus prompted me whether to create the
folder. This is a convenient, and I assume desired functionality.
Today, I witnessed a different behavior. Gnus appeared to attempt the
move without first checking for the folder's existence on the server.
See the backtrace below.
,----
| Debugger entered--Lisp error: (error "gmail+nnimap+gmail:identica/imap Name or service not known")
| make-network-process(:name "*nnimap*" :buffer #<buffer *nnimap gmail+nnimap+gmail:identica nil *nntpd**<2>> :host "gmail+nnimap+gmail:identica" :service "imap")
| open-network-stream("*nnimap*" #<buffer *nnimap gmail+nnimap+gmail:identica nil *nntpd**<2>> "gmail+nnimap+gmail:identica" "imap")
| proto-stream-open-starttls("*nnimap*" #<buffer *nnimap gmail+nnimap+gmail:identica nil *nntpd**<2>> "gmail+nnimap+gmail:identica" "imap" (:end-of-command "\n" :type network :return-list t :shell-command "ssh %s imapd" :capability-command "1 CAPABILITY\n" :success " OK " :starttls-function #[(capabilities) "\305\b\306\x1a\307\310\v\n #,\205
| open-protocol-stream("*nnimap*" #<buffer *nnimap gmail+nnimap+gmail:identica nil *nntpd**<2>> "gmail+nnimap+gmail:identica" "imap" :type network :return-list t :shell-command "ssh %s imapd" :capability-command "1 CAPABILITY\n" :success " OK " :starttls-function #[(capabilities) "\305\b\306\x1a\307\310\v\n #,\205
| nnimap-open-connection-1(#<buffer *nntpd*>)
| nnimap-open-connection(#<buffer *nntpd*>)
| nnimap-open-server("gmail+nnimap+gmail:identica")
| nnimap-possibly-change-group(nil "gmail+nnimap+gmail:identica")
| nnimap-request-accept-article("identica" "gmail+nnimap+gmail:identica" t)
| gnus-request-accept-article("nnimap+gmail:identica" nil t t)
| eval((gnus-request-accept-article "nnimap+gmail:identica" (quote nil) t t))
| nnimap-request-move-article(16046 "INBOX" "gmail" (gnus-request-accept-article "nnimap+gmail:identica" (quote nil) t t) t nil)
| gnus-request-move-article(16046 "nnimap+gmail:INBOX" "gmail" (gnus-request-accept-article "nnimap+gmail:identica" (quote nil) t t) t nil)
| gnus-summary-move-article(nil)
| call-interactively(gnus-summary-move-article nil nil)
`----
next reply other threads:[~2011-04-06 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 18:57 Joseph Gay [this message]
2011-04-12 15:04 ` Bojan Nikolic
2011-04-12 16:01 ` Lars Magne Ingebrigtsen
2011-04-12 18:02 ` Joseph Gay
2011-04-12 18:49 ` 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=874o6bky2p.fsf@geneva.hpsy.me \
--to=gilleylen@gmail.com \
--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).