So --
the client runs something like this:
//---
#!/bin/bash
REMOTE_HOME=/home/myself
LOCAL_HOME=/home/myself
if [ "$#" -ne 1 ]
then
echo "Please give the maildir name!"
exit 1
fi
declare -A local_config
local_config=(
["personal"]="$LOCAL_HOME/.notmuch-config.personal"
Hello,
Sorry, it seems that the code in me previous email was removed by nabble.
I'll post again from a real email client :-)
Regarding your first question: yes, it's my primary mail server. I use a
virtual machine
at Linode.
J.
--
Sent from: http://notmuch.198994.n3.nabble.com/
This is much worse than normal problems with large files or long lines. There’s
something worse-than-quadratic in the nesting and indenting elisp. I’ve been
meaning to get around to figuring out what, but no luck yet.
--
Brian Sniffen
> On Jan 18, 2019, at 7:03 PM, Landry, Walter wrote:
>
Hi Landry,
I am afraid this is a common limitation of emacs: if you start opening
large files (especially with long lines) it becomes very slow.
A viable workaround is to open the offending thread in the tree view
(bound to 'z' by default) and then only view individual messages.
Cheers,
Dan
Hello Everyone,
I am using the emacs frontend to notmuch. It has mostly been a pleasant
experience, but I am having a problem with large threads. Essentially,
when I try to view a large thread, the machine locks up for many
minutes. The problem seems very similar to these posts.
Hello
I've been using notmuch successfully for a couple of years now (mostly
via neomutt). Thanks for developing it.
Not long ago I switched my mail setup to use notmuch insert via
mailfilter instead of good old procmail. However, since then a number
of emails are reported by notmuch as
