Richard Russon

> I guess we could ... check the keyring to see if we can find a name for the recipient That would look pretty cool, **but**... I suspect it could...

More v2 ideas... We're displaying the **sub**-key that was used to encrypt. **Can we get to the main key?** (which would be more recognisable to people) e.g. For my key,...

I've tried a few shells and I can reproduce your problem with `tcsh -c neomutt` (bash, dash, ksh, zsh work for me) and any shell script. (I see the same...

The IMAP code is flaky, but it may be a while before we risk making significant changes. I'm going to close this as "unfixable" for now. Sorry.

Thanks for pushing ahead with this, @balejk. Sorry for avoiding the issue. This is one of those complicated bits of old code. Nobody really understands them and nobody's brave enough...

I haven't started yet -- I'm deep in quite a few other things, > it might be rather a while until I have time for it There's no rush. The...

Thanks for your work on this! The code changes look fine to me. As for the second commit, I don't know. You have a much better understanding of whether it's...

It's a feature that was added nearly two years ago: 48908fb9a7c6. The browser is a complicated beast. It's used for: - file/dir selection - local mailbox selection (mailbox, mbox, etc)...

What's your config? ``` neomutt -Q index_format -Q crypt_chars ``` --- It _sounds_ like a refresh problem, but I can't think why the crypto status wouldn't be known on the...

Ah! That's me `git rebase`ing my work branch over `main` so that I have the latest source.