From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: imap or offlineimap ?
Date: Fri, 18 Feb 2011 15:07:24 -0800 [thread overview]
Message-ID: <87oc690wnn.fsf@gnus.org> (raw)
In-Reply-To: <87aahtukyi.fsf@andy.bu.edu>
Andrew Cohen <cohen@andy.bu.edu> writes:
> I guess I could special-case the raw imap search and treat
> header-limited searches differently. I generally don't like this kind of
> special casing, but I'll think again if there is a better way.
How about sorting the groups on the method first (i.e., nnimap, nntp,
etc), and then issuing the prompt once per method type? I think that
would give you the correct number of prompts for all use cases.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-02-18 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 8:12 Erik Colson
2011-02-18 8:16 ` Lars Ingebrigtsen
2011-02-18 8:25 ` Erik Colson
2011-02-18 8:57 ` Tassilo Horn
2011-02-18 9:42 ` Erik Colson
2011-02-18 10:07 ` Tassilo Horn
2011-02-18 20:49 ` Andrew Cohen
2011-02-18 23:07 ` Lars Ingebrigtsen [this message]
2011-02-22 17:39 ` Andrew Cohen
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=87oc690wnn.fsf@gnus.org \
--to=larsi@gnus.org \
--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).