From: Tommy Kelly <tommy.kelly@verilab.com>
To: ding@gnus.org
Subject: Re: rnnimap resplitting
Date: Sun, 05 Dec 2010 21:03:27 +0000 [thread overview]
Message-ID: <m2bp50exuo.fsf@verilab.com> (raw)
In-Reply-To: <m34oashwd9.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> I don't see why... I've now added the `respool' token to nnimap, so it
> should allow this.
I'm still not getting this. I pulled your changes but when I do a 'B r',
it still offers nnimap as the backend, but if I explicitly type in
"nniap" it tells me [No Match]. It aso gives me that response if I
double-tab in the field. Howeve, if I hit enter with the field empty --
i.e. accepting the default offering of "nnimap" -- then it seems to
accept that and asks me for the server.
I don't know what to enter there, but double-tabbing gives "[No Match]"
as does anything else I enter. Hitting return with an empty server field
returns an error message "No method given for respooling".
Tommy
next prev parent reply other threads:[~2010-12-05 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 17:44 Tommy Kelly
2010-12-05 19:07 ` Lars Magne Ingebrigtsen
2010-12-05 21:03 ` Tommy Kelly [this message]
2010-12-05 21:11 ` 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=m2bp50exuo.fsf@verilab.com \
--to=tommy.kelly@verilab.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).