From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: More on the new nnimap
Date: Fri, 08 Oct 2010 11:47:13 -0400 [thread overview]
Message-ID: <m38w28hejq.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <m3mxqpakd6.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 07 Oct 2010 21:11:33 +0200")
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Dan Christensen <jdc@uwo.ca> writes:
>> Could that "possibly" be the issue here? The original post said "it
>> should not be an error if the group already exists on the server." I
>> agree that that shouldn't be an error.
LMI> I don't know... if you ask Gnus to create a group on the server, it
LMI> should give an error if that isn't possible.
The other backends seem to all just accept that it already exists and
subscribe to it. Since the function looks like:
(deffoo nnimap-request-create-group (group &optional server args)
(when (nnimap-possibly-change-group nil server)
(with-current-buffer (nnimap-buffer)
(car (nnimap-command "CREATE %S" (utf7-encode group t))))))
How about passing group rather than nil to (nnimap-possibly-change-group),
returning if it exists and only creating if it does not?
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next prev parent reply other threads:[~2010-10-08 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 18:23 James Cloos
2010-10-04 16:36 ` Lars Magne Ingebrigtsen
2010-10-04 18:02 ` James Cloos
2010-10-04 19:48 ` Lars Magne Ingebrigtsen
2010-10-04 21:14 ` James Cloos
2010-10-05 16:39 ` Lars Magne Ingebrigtsen
2010-10-05 22:01 ` Dan Christensen
2010-10-07 19:11 ` Lars Magne Ingebrigtsen
2010-10-08 15:47 ` James Cloos [this message]
2010-10-06 9:05 ` James Cloos
2010-10-07 19:22 ` Lars Magne Ingebrigtsen
2010-10-08 16:00 ` James Cloos
2010-10-09 16:06 ` 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=m38w28hejq.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.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).