From: John Sullivan <john@wjsullivan.net>
To: ding@gnus.org
Subject: Re: Moving nnimap articles failing with "has no process" error
Date: Thu, 04 Nov 2010 11:27:50 -0700 [thread overview]
Message-ID: <8762wdj655.fsf@myles.home.wjsullivan.net> (raw)
In-Reply-To: <874obyuzyo.fsf@myles.home.wjsullivan.net>
John Sullivan <john@wjsullivan.net> writes:
> This maybe seems to only happen when trying to move articles to a group
> which has not been entered yet since upgrading. After entering the
> target group, this move now seems to work..
No, I was wrong about that, it's still happening. It moves one message
successfully and then fails.
--
John Sullivan
Emacs Planner Maintainer
http://wjsullivan.net/PlannerMode.html
next prev parent reply other threads:[~2010-11-04 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 21:51 John Sullivan
2010-11-03 1:31 ` John Sullivan
2010-11-18 23:39 ` John Sullivan
2010-11-03 16:35 ` John Sullivan
2010-11-04 18:27 ` John Sullivan [this message]
2010-11-04 20:07 ` Lars Magne Ingebrigtsen
2010-11-16 18:44 ` John Sullivan
2010-11-21 5:15 ` Lars Magne Ingebrigtsen
2010-12-07 18:08 ` John Sullivan
2010-12-10 18:34 ` John Sullivan
2010-12-15 20:50 ` 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=8762wdj655.fsf@myles.home.wjsullivan.net \
--to=john@wjsullivan.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).