From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: gnus-sync and the new nnimap (Was: tramp and the new nnimap?)
Date: Tue, 14 Sep 2010 10:05:03 +0200 [thread overview]
Message-ID: <yb08w34px74.fsf@dod.no> (raw)
In-Reply-To: <yb0hbhspxm8.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> Question for Ted: With the new and (seriously) performance-improved
> nnimap, and with imap.el going away, is it an idea to make the IMAP
> storage of tramp work through nnimap?
If that proves to be impossible: would it be possible to have gnus-sync
work directly with nnimap? That would make it possible for it have the
same offline/online behaviour as nnimap itself.
next prev parent reply other threads:[~2010-09-14 8:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 7:55 tramp and the new nnimap? Steinar Bang
2010-09-14 8:05 ` Steinar Bang [this message]
2010-09-14 10:47 ` gnus-sync and the new nnimap Ted Zlatanov
2010-09-14 10:54 ` Lars Magne Ingebrigtsen
2010-09-14 11:09 ` Ted Zlatanov
2010-09-14 12:22 ` Jose A. Ortega Ruiz
2010-09-14 13:17 ` Ted Zlatanov
2010-09-14 17:08 ` Štěpán Němec
2010-09-14 17:10 ` Lars Magne Ingebrigtsen
2010-09-14 12:50 ` Štěpán Němec
2010-09-14 12:54 ` Lars Magne Ingebrigtsen
2010-09-14 15:31 ` Lawrence Mitchell
2010-09-14 16:48 ` Štěpán Němec
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=yb08w34px74.fsf@dod.no \
--to=sb@dod.no \
--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).