Crispin Bennett

> In your case, I can't help but wonder if it'd be easier to set a custom content view instead of messing around with the background view. Easier, yes, but...

@aarongraham Are you currently working on this? If not, I'd be interested in picking it up (it's a feature I want!). @axelson - are you still open to a PR...

Thanks @aarongraham - if I was writing a standalone VSCode extension, I'd consider tree-sitter because the api looks nice. As it is, I guess it wouldn't be a good fit...

I see your point, though I'm undecided on whether your intuition is right: I suspect dotfiles are rare enough in Windows that anyone using them does so in a unixy...

@GowthamKudupudi - no, it completely dropped off my radar.

Do you get the same (correct, or at least expected) behaviour if the message you have open for reading was the last unseen message present in the header view? That's...

I've recently started using mu4e and find this a significant usability problem. It makes my workflow (read, then archive/refile) difficult as (with a short update interval) the header often disappears...

I agree an asynchronous email workflow can be viable, even preferable. But there are people who prefer otherwise, and circumstances that dictate it, in which cases the current mu4e behaviour...

OK thanks. A reasonable workaround for now would be to use an unread search for asynchronous sweeps, but switch to the inbox maildir when keeping an eye on things.

I'm on Emacs 26.3 and mu 1.2.0. Update interval is 2m - shorter than needed really but I've just circled the wagons back to local maildirs after some years on...