I tried to repro this with HEAD opening ~40 email tabs at once and couldn't repro it. Can you verify if this is still a bug? If not, this can be closed.
Just tried to repro this and it seems to be fixed, can you verify? This bug can be closed.
I use neovim as my $EDITOR. When I go into the compose::editor context and put neovim into insert mode, pressing the key seems to switch my aerc tab, not insert a tabstop like neovim would. I ensured that my
binds.confdoesn't contain any global or context-specific bindings for , and that compose::editor has
$noinherit = true. What is the source of this default binding? Is this binding embedded somewhere in the code by default?
When trying to read a multipart email with one of the parts using PGP-SHA256, the following error is reported:
pgpmail: unsupported micalg "PGP-SHA256"
There is also a text/plain part not using PGP, but I'm not able to read it because of the error. Should aerc gracefully fail in this case and keep checking other parts in the multipart message to see if anything else is renderable normally? This essentially blocks me from reading emails with any PGP errors on them.
Thanks for the lists archive link, I will get to work on this patch.
I am trying to add aerc to home-manager. When home-manager generates the aerc config, it places a read-only symlink pointing to a world-readable
accounts.conffile in the nix store. However, with this method, I cannot run aerc as it returns with an error and the following message:
The file /home/xxx/.config/aerc/accounts.conf has too open permissions. This is a security issue (it contains passwords). To fix it, run `chmod 600 /home/xxx/.config/aerc/accounts.conf` Failed to load config: account.conf permissions too lax
I cannot simply chmod it to the required permissions since the filesystem containing the
accounts.conffile is read-only. I can also guarantee that there are no secrets in the generated
accounts.conffile, since home-manager only adds a
outgoing-cred-cmdto the file.
What is the best way forward? In cases like this where the user can guarantee that there are no secrets in
accounts.conf, the security error shouldn't block the user from running
aerc. Instead, if it was a warning (and especially one that can be disabled somehow), that would be useful for users on other platforms.
Would you be able to clarify why you've chosen to not have JMAP support? I'm just curious, since it seems like a beneficial feature.