From: Anton Khirnov <anton@khirnov.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [RFC] vim plugin rewrite II
Date: Sun, 15 Jan 2012 16:34:08 +0100 [thread overview]
Message-ID: <20120115153408.30382.40507@daenerys.khirnov.net> (raw)
In-Reply-To: <87r4z1iudw.fsf@zancas.localnet>
On Sat, 14 Jan 2012 22:15:07 -0400, David Bremner <david@tethera.net> wrote:
> On Sat, 14 Jan 2012 08:54:43 +0100, anton@khirnov.net wrote:
> >
> > The advantages over current vim client are still the following:
> > * sending and displaying/saving attachments
> > * much better unicode support
> > * tag name and search commands completion
> > * proper representation of the thread structure
> > * easier to extend thanks to python's massive standard library
> >
> > Please comment.
>
> Hi Anton;
>
> I'm not a vim user, so I probably can't say anything very helpful, but
> it does sound like some nice improvements. Hopefully one of our vim
> front-end users can comment a bit more. One thing I wondered about is
> if your version is still completely synchronous, with the resulting
> problems dealing with large (say, more than 10000 messages) search
> results?
>
Yes, it's still synchronous. I suppose making it asynchronous shouldn't
be all that hard, i just never found enough time and motivation for that
(it was never a huge problem here).
--
Anton Khirnov
next prev parent reply other threads:[~2012-01-15 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 7:54 [RFC] vim plugin rewrite II anton
2012-01-15 2:15 ` David Bremner
2012-01-15 15:34 ` Anton Khirnov [this message]
[not found] ` <87mx9n7dq4.fsf@servo.finestructure.net>
2012-01-16 19:04 ` Anton Khirnov
2012-04-18 14:21 ` Felipe Contreras
2012-04-18 14:42 ` Felipe Contreras
2012-04-19 16:36 ` Felipe Contreras
2012-05-02 20:23 ` Anton Khirnov
2012-05-04 11:19 ` Felipe Contreras
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120115153408.30382.40507@daenerys.khirnov.net \
--to=anton@khirnov.net \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).