On 19Nov2022 09:21, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 02:32:25PM +1100, Cameron Simpson wrote:
Maybe the docs should have a small mention around `~h` that it
cannot utilise the header cache.
There is a note, "***)", next to ~b, ~B, ~h, ~M, and ~X that mentions
they entail
On 19Nov2022 09:16, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 02:15:05PM +1100, Cameron Simpson wrote:
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
The headers are colored as they are displayed, but also when any
flags are updated.
If it's only colouring the visible index listing,
On Sat, Nov 19, 2022 at 02:32:25PM +1100, Cameron Simpson wrote:
Maybe the docs should have a small mention around `~h` that it cannot
utilise the header cache.
There is a note, "***)", next to ~b, ~B, ~h, ~M, and ~X that mentions
they entail reading the whole message in and recommends not
On Sat, Nov 19, 2022 at 02:15:05PM +1100, Cameron Simpson wrote:
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
The headers are colored as they are displayed, but also when any
flags are updated.
If it's only colouring the visible index listing, that's fine with me.
No, it's not. I will fix
On 18Nov2022 23:08, Kurt Hackenberg wrote:
On Sat, Nov 19, 2022 at 02:25:50PM +1100, Cameron Simpson wrote:
from https://www.rfc-wiki.org/wiki/RFC2822. Is there a better RFC 2822
page? I used to use a nicely formatted tools.ietf.org URL, but that now
redirects to some RFC author editing ...
On Sat, Nov 19, 2022 at 02:25:50PM +1100, Cameron Simpson wrote:
from https://www.rfc-wiki.org/wiki/RFC2822. Is there a better RFC 2822
page? I used to use a nicely formatted tools.ietf.org URL, but that now
redirects to some RFC author editing ... thing.
Is this better? (For RFC 5322,
On 19Nov2022 14:25, Cameron Simpson wrote:
Anyway, I'll try plain `~f "cameron simnpson"` and see how it goes.
This is nice and fast:
color index white default "((~P|(%f polyname ~f 'cameron simpson'))) | (~v
~((~P|(%f polyname ~f 'cameron simpson'"
and does the same colouring I
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder
contents, instead of only the lines being displayed. That is a
massive performance hit for a big folder. Is that the case?
On 18Nov2022 18:48, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 01:16:47PM +1100, Cameron Simpson wrote:
On 19Nov2022 08:32, Cameron Simpson wrote:
The issue is my index colouring, specificly this line:
color index white default "((~P|%f polyname ~h '^from:.*cameron simpson')) | (~v
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder
contents, instead of only the lines being displayed. That is a
massive performance hit for a big folder. Is that the case?
On Sat, Nov 19, 2022 at 01:16:47PM +1100, Cameron Simpson wrote:
On 19Nov2022 08:32, Cameron Simpson wrote:
The issue is my index colouring, specificly this line:
color index white default "((~P|%f polyname ~h '^from:.*cameron simpson')) | (~v
~((~P|%f polyname ~h '^from:.*cameron
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder contents,
instead of only the lines being displayed. That is a massive
performance hit for a big folder. Is that the case?
The headers are colored as they are
On 19Nov2022 08:32, Cameron Simpson wrote:
The issue is my index colouring, specificly this line:
color index white default "((~P|%f polyname ~h '^from:.*cameron simpson')) | (~v
~((~P|%f polyname ~h '^from:.*cameron simpson')))"
This colours messages as white if they're from me or from
On 19Nov2022 07:55, Cameron Simpson wrote:
On 18Nov2022 09:38, Kevin J. McCarthy wrote:
source ~/rc/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Yes, Mutt's internal structures used for aliases are not designed for
that many.
It's not the number of aliases. I've just stripped
On 18Nov2022 09:38, Kevin J. McCarthy wrote:
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.
Yes, Mutt's internal structures used for aliases are not designed for
that many. It
On Fri, Nov 18, 2022 at 09:06:30PM +1100, Cameron Simpson wrote:
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
On 15Nov2022 20:10, Kevin J. McCarthy 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
On Wed, Nov 16, 2022 at 11:43:39AM +1100, Cameron Simpson wrote:
The stuff before the "Sorting mailbox..." phase seems ... fast enough.
During the "Sorting mailbox..." phase I see mutt reading message files
I'd not expect it to need to touch, _and_ making some temporary files.
Example `lsof`
I'm using my python folder (a Maildir) because it is large enough to do
a little live debugging on. Summary header:
c...@cskk.id.au reverse-threads/last-date 0% 1152M Msgs:140928 New:90812
Del:0 Flag:608 =python
I'm using a header cache, and my sort is reverse-threads/last-date.
Command
19 matches
Mail list logo
