From: soyeomul@doraji.xyz (황병희)
To: help-gnu-emacs@gnu.org
Subject: Re: Any tricks to speedup nnimap?
Date: Sun, 10 Nov 2019 20:40:37 +0900 [thread overview]
Message-ID: <yw.149.385ut2q0yh.fsf@delta.birch.chromebook> (raw)
In-Reply-To: <m2k18zu1mx.fsf@gmail.com> (Pankaj Jangid's message of "Sun, 20 Oct 2019 16:25:50 +0530")
> I just tried it. It works really well. But there is another problem. I
> keep only 1000 messages locally. There is a setting in mbsync to do
> that. I just realized that searching through all the mails will be not
> be possible using this approach.
So i use Gmail web interface for searching in detail. With speed, just
reading/followup is best Eric's way -- mbox's downloading to local hard
disk -- for now.
Well i heard that somebody is making for Gnus' cloud. That will be great
news someday far later, i think.
Sincerely,
--
^고맙습니다 _地平天成_ 감사합니다_^))//
prev parent reply other threads:[~2019-11-10 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 19:24 Any tricks to speedup nnimap? Pankaj Jangid
2019-10-19 20:56 ` Eric Abrahamsen
2019-10-20 10:55 ` Pankaj Jangid
2019-11-10 11:40 ` 황병희 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw.149.385ut2q0yh.fsf@delta.birch.chromebook \
--to=soyeomul@doraji.xyz \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).