On 15Nov2022 20:10, Kevin J. McCarthy <[email protected]> wrote:
That `cur` message file dates from 2021-07-15 17:36:10 GMT (long ago)
and the temporary file is indeed temporary - it vanishes. I speculate
that mutt's... unpacking the source message in some way?
Seems likely, but off the top of my head I can't guess what's doing it.
[...]
Thanks for the response. I've been experimenting tonight.
It isn't the sort. As you suggest, it is in a process after the sort.
Starting with an empty config except for a header cache dir setting, I
notices a distinct slowdown of the scan at about 80%. Odd. So I moved
the cache sideways and let it rebuild:
43869952 18 Nov 20:43 02a1cc9292e0222624346e5ff8742f34
73852160 18 Nov 20:09 02a1cc9292e0222624346e5ff8742f34-ASIDE
This brought a nice linear scan.
At this point the folder loads pretty promptly.
Turning on my normal settings including sort made no difference, still
nice and fast. Even my macros to collapse/uncollapse certain patterns
seem basicly free.
So I started adding back in my config files (I source a few). Here's the
glaring one:
source ~/rc/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Really, it is a bit excessive. Particularly since I think I don't ever
use aliases anyway.
With that commented out the python folder's still nice and fast.
What's weird to me is that the effect it has seems dependent on the
folder I choose. Reading the file itself doesn't seem to slow; it seems
to be some interaction with the folder.
Cheers,
Cameron Simpson <[email protected]>
