Feature request: a ".noupdate" file

[cpence]

I've got an interesting (but, I think, common) use-case -- not knowing how the internals of mu work, I've got no idea whether or not this would be easy to do. Like many people, I've got a handful of (big!) mail folders that I can be certain will never be updated again -- storage/2004, storage/2005, etc. I know that if I index them, then add a .noindex file to their root, then they will stay in the index but not be scanned again in the future. But then, if I run a mu index --rebuild, I lose those messages. What I'd love to see would be a .noupdate file, similar to .noindex. If there's a .noupdate file in a Maildir, then if there are any messages from this folder already in the index, the folder won't be scanned on a mu index. During a mu index --rebuild, though, there aren't any messages from this folder already in the index, so it will get scanned once. (Something like .scanonce would also be a good name for this file.)

Would that be a plausible thing to implement, or does it run afoul of the indexing architecture somehow?

[djcb]

Hi, I have added '.noupdate' support (in the git version), it does (or should do!) more-or-less what you ask for; the only caveat is that it requires an explicit "mu index --rebuild" to index the messages in maildirs with .noupdate initially

[cpence]

Awesome! I went from having ~57,000 messages to scan every time I check mail in mu4e to 4,127. Makes it way faster to check mail! Thanks!