Hello,
On 2021-09-25 10:26, David Bremner writes:
> I think it is a bug in doom or straight, or at least an assumption that
> turns out to be wrong. They are assuming the elisp is runnable from git,
> but in fact it needs to run make to create notmuch-version.el. I think
> the straight recipe
Alan Schmitt writes:
>
> The surprising thing is that there is not file
> ~/.emacs-configs/doom-emacs/.local/straight/repos/notmuch/emacs/notmuch-version.el,
> just a file
> ~/.emacs-configs/doom-emacs/.local/straight/repos/notmuch/emacs/notmuch-version.el.tmpl
> so this is probably why the
Hello,
On 2021-09-24 20:33, David Bremner writes:
> That will teach me not to ask people to check M-x notmuch-version!
I did at the time, and it reported "0.33.1". So I investigated a bit.
If I search for the `notmuch-version' function, I find it in
Alan Schmitt writes:
> Hello David,
>
> I found the source of the issue, and I would like to apologize because
> it’s fully my fault. I’ve realized I was not using the elisp code from
> the package installed using my package manager, but one installed using
> straight that was pinned to an old
Hello David,
I found the source of the issue, and I would like to apologize because
it’s fully my fault. I’ve realized I was not using the elisp code from
the package installed using my package manager, but one installed using
straight that was pinned to an old version. I simply switched to the
Alan Schmitt writes:
>
> I can view a thread with more than 7000 messages (with
> show-only-matching-messages to t) if they are not encrypted. In fact I
> already could with 0.32 if I remember correctly. The fact that messages
> are encrypted seems to matter here.
I've been unable to replicate
Hello,
On 2021-09-22 11:25, Tomi Ollila writes:
>>> e.g (set max-lisp-eval-depth 1600)
>>
>> Thank you for the suggestion. I tried with 1600, and I get a different
>> error (and the numbers are larger now).
>>
>> Debugger entered--Lisp error: (error "Variable binding depth exceeds
>>
On Wed, Sep 22 2021, Alan Schmitt wrote:
> On 2021-09-21 21:27, Tomi Ollila writes:
>
>> I'd be interested to know if changing max-lisp-eval-depth to a larger value
>> made difference.
>>
>> e.g (set max-lisp-eval-depth 1600)
>
> Thank you for the suggestion. I tried with 1600, and I get a
On 2021-09-21 21:27, Tomi Ollila writes:
> I'd be interested to know if changing max-lisp-eval-depth to a larger value
> made difference.
>
> e.g (set max-lisp-eval-depth 1600)
Thank you for the suggestion. I tried with 1600, and I get a different
error (and the numbers are larger now).
On Tue, Sep 21 2021, Alan Schmitt wrote:
> On 2021-09-21 09:42, David Bremner writes:
>
>> That's not completely unexpected. The change in question only really fixes
>> it for
>> unthreaded view. Try notmuch-unthreaded-from-search-current-query (bound
>> to 'U' by default).
>
> Thank you for
Hello,
On 2021-09-21 12:38, David Bremner writes:
> Alan Schmitt writes:
>
>> Thank you for bearing with me. I confirm that I can see messages at the
>> beginning of the thread using both an unthreaded search and
>> notmuch-show-only-matching-messages set to t. Unfortunately, messages
>> later
Alan Schmitt writes:
> On 2021-09-21 09:42, David Bremner writes:
>
>> That's not completely unexpected. The change in question only really fixes
>> it for
>> unthreaded view. Try notmuch-unthreaded-from-search-current-query (bound
>> to 'U' by default).
>
> Thank you for bearing with me. I
On 2021-09-21 09:42, David Bremner writes:
> That's not completely unexpected. The change in question only really fixes it
> for
> unthreaded view. Try notmuch-unthreaded-from-search-current-query (bound
> to 'U' by default).
Thank you for bearing with me. I confirm that I can see messages at
Alan Schmitt writes:
> Hello,
>
> I’m on notmuch 0.33.1 and I’m still having issues displaying messages in
> long threads when the messages are encrypted. I have such a thread with
> more than 600 messages, and when I do the following:
> - search for the messages
> - run
Hello,
I’m on notmuch 0.33.1 and I’m still having issues displaying messages in
long threads when the messages are encrypted. I have such a thread with
more than 600 messages, and when I do the following:
- search for the messages
- run notmuch-tree-from-search-current-query
I get an error (I
Alan Schmitt writes:
> On 2021-08-20 09:55, David Bremner writes:
>
>> The commit I mentioned is not in 0.32.3.
>
> Ah, sorry, I thought a release included what was in master at that time.
> I guess I should wait for 0.33?
>
Right, it should be just a few weeks.
d
On 2021-08-20 09:55, David Bremner writes:
> The commit I mentioned is not in 0.32.3.
Ah, sorry, I thought a release included what was in master at that time.
I guess I should wait for 0.33?
Best,
Alan
signature.asc
Description: PGP signature
___
Alan Schmitt writes:
> On 2021-08-01 23:11, David Bremner writes:
>
>> With commit 37f84d6d2 (only in master currently), much larger threads
>> should be displayable in unthreaded view, e.g using M-x
>> notmuch-unthreaded
>
> I just updated to 0.32.3, and I confirm a message is displayed quite
Hello,
On 2021-08-01 23:11, David Bremner writes:
> With commit 37f84d6d2 (only in master currently), much larger threads
> should be displayable in unthreaded view, e.g using M-x
> notmuch-unthreaded
I just updated to 0.32.3, and I confirm a message is displayed quite
fast (if I set
Alan Schmitt writes:
> Hello,
>
> On 2020-01-15 21:15, Örjan Ekeberg writes:
>
>> I have a vague recollection that someone pointed out that it is the
>> indentation that takes most of the time and that turning off indentation
>> speeds up the display of huge threads.
>
> I've been trying this
Hello,
On 2020-01-15 21:15, Örjan Ekeberg writes:
> I have a vague recollection that someone pointed out that it is the
> indentation that takes most of the time and that turning off indentation
> speeds up the display of huge threads.
I've been trying this by setting:
(setq
Hi Örjan,
On 2020-01-15 21:15, Örjan Ekeberg writes:
> I think opening the thread with C-U RET instead of RET does exactly
> that, i.e. only shows the matching messages.
>
> In less extreme cases, using tree view (ALT-RET) may be an option since
> it does not have to format the contents of the
Hi Alan,
Alan Schmitt writes:
>
> September 07 [13/5767]
>
> It takes forever to display (I've waited a few minutes and it was still
> stuck). I know it's a lot of messages, so is there a way to just display
> the 13 that match? Or to limit the total number of messages displayed?
I think
Hello,
I have some performance issues when displaying a huge thread, like this:
September 07 [13/5767]
It takes forever to display (I've waited a few minutes and it was still
stuck). I know it's a lot of messages, so is there a way to just display
the 13 that match? Or to limit the total
24 matches
Mail list logo