From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>,
Matthew Lear <matt@bubblegen.co.uk>,
notmuch@notmuchmail.org
Subject: Re: emacs / vim - time taken to open threads
Date: Wed, 25 Mar 2015 09:54:55 +0200 [thread overview]
Message-ID: <m2d23xv7e8.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87384u6lgb.fsf@maritornes.cs.unb.ca>
On Wed, Mar 25 2015, David Bremner <david@tethera.net> wrote:
> Matthew Lear <matt@bubblegen.co.uk> writes:
>
>>
>> Despite being a vi guy for years, I prefer the emacs interface to
>> notmuch and really like what it provides. I'm sticking with it but there
>> is clearly a problem and I'd like to solve it. It's annoying when you
>> know that something isn't working as well as it should be.
>>
>> Is it known that emacs is slower with notmuch or do you think I have
>> some kind of build / environment problem? Or could it be due to some of
>> the email content (doubtful) or something else such as encoding etc?
>
> My experience is that the emacs interface is faster than the vim one.
> At least I don't have an examples handy where emacs is slower than the
> vim interface at rendering a thread. At a wild guess, I suspect it has
> to do with how many attachments there are, and the emacs UI being
> overenthusiastic about processing attachements.
I've seen over 15 seconds of load time when opening some 20+ message
thread -- and jumping through messages has been slow in emacs ui.
I have not got time to investigate this further...
>
> d
Tomi
next prev parent reply other threads:[~2015-03-25 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 21:58 emacs / vim - time taken to open threads Matthew Lear
2015-03-24 23:10 ` David Bremner
2015-03-25 7:54 ` Tomi Ollila [this message]
2015-03-25 11:21 ` Matthew Lear
2015-04-01 4:08 ` David Bremner
2015-04-11 18:09 ` Matthew Lear
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=m2d23xv7e8.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=matt@bubblegen.co.uk \
--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).