From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: tramp-devel@mail.freesoftware.fsf.org
Subject: Re: gnus-sync and the new nnimap
Date: Tue, 14 Sep 2010 05:47:46 -0500 [thread overview]
Message-ID: <8739tcd2jx.fsf@lifelogs.com> (raw)
In-Reply-To: <yb08w34px74.fsf@dod.no>
On Tue, 14 Sep 2010 10:05:03 +0200 Steinar Bang <sb@dod.no> wrote:
>>>>>> 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?
Tramp would then require nnimap, which is not so good. In fact,
tramp-imap.el is currently broken (because imap-hash.el used the removed
imap-fetch-safe) and I'm waiting for the dust to settle before fixing
it. The lack of an outcry tells me they are not widely used and I'm
considering removing them form Tramp altogether. If there are no users
for a feature, no matter how great you think it is...
SB> If that proves to be impossible: would it be possible to have gnus-sync
SB> work directly with nnimap? That would make it possible for it have the
SB> same offline/online behaviour as nnimap itself.
Yes. That may be the better approach, especially if tramp-imap.el goes
away. But it also need UI work so for now it's on my TODO list but not
at the top.
Ted
next prev parent reply other threads:[~2010-09-14 10:47 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 ` gnus-sync and the new nnimap (Was: tramp and the new nnimap?) Steinar Bang
2010-09-14 10:47 ` Ted Zlatanov [this message]
2010-09-14 10:54 ` gnus-sync and the new nnimap 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=8739tcd2jx.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=tramp-devel@mail.freesoftware.fsf.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).