High CPU usage on refresh

[arximboldi]

Hi!

Thanks for building this interface, I really like how it has a lot of UX details that make it so much faster to use than the standard Notmuch UI.

However, I have the problem that when opening the nm buffer or refreshing it, emacs stays for a long time (few minutes) using one core fully, and in the background there is also a notmuch show ... process. I guess it is related to the high amount of emails -- I have 140152 results in my inbox -- but as notmuch says, that'ts not much email ;-)

Do you have any ideas on how to work around this? Making maybe the results buffer load results lazily?

[arximboldi]

I also get this warning on refresh (g key):

Warning (undo): Buffer ‘*nm*’ undo info was 15782627 bytes long.
The undo info was discarded because it exceeded `undo-outer-limit'.

This is normal if you executed a command that made a huge change
to the buffer.  In that case, to prevent similar problems in the
future, set `undo-outer-limit' to a value that is large enough to
cover the maximum size of normal changes you expect a single
command to make, but not so large that it might exceed the
maximum memory allotted to Emacs.

If you did not execute any such command, the situation is
probably due to a bug and you should report it.

You can disable the popping up of this buffer by adding the entry
(undo discard-info) to the user option `warning-suppress-types',
which is defined in the `warnings' library.

Warning (undo): Buffer ‘*nm*’ undo info was 15782775 bytes long.
The undo info was discarded because it exceeded `undo-outer-limit'.

This is normal if you executed a command that made a huge change
to the buffer.  In that case, to prevent similar problems in the
future, set `undo-outer-limit' to a value that is large enough to
cover the maximum size of normal changes you expect a single
command to make, but not so large that it might exceed the
maximum memory allotted to Emacs.

If you did not execute any such command, the situation is
probably due to a bug and you should report it.

You can disable the popping up of this buffer by adding the entry
(undo discard-info) to the user option `warning-suppress-types',
which is defined in the `warnings' library.