Alejandro Colomar

Hi! I've been improving the parsing of integers in shadow for some years, fixing several bugs in the process. We've come up with a set of APIs that I've packaged...

Hi, On 4/9/23 19:20, Sebastian Carlos wrote: > I agree. I would also like to note that the [website](https://man7.org/linux/man-pages/index.html) itself is outdated. It took a while for me to realize...

v1b (by @flatcap) changes: - Rebase on main ``` $ git range-diff 2dde10ea0^..2dde10ea0 neomutt/main..gh/gpg 1: 2dde10ea0 = 1: f09907fe9 ncrypt/crypt_gpgme.c: Show encryption information ```

v1c changes: - Rebase on main - Add some links to the commit message ``` $ git range-diff gh/gpg^..gh/gpg neomutt/main..gpg 1: f09907fe9 ! 1: 7ed3c312c ncrypt/crypt_gpgme.c: Show encryption information @@...

(BTW, @flatcap , the feature page for the -C flag hasn't been updated with the recent fix (s/neomuttrc/gitconfig/).)

> > the feature page for the -C flag hasn't been updated with the recent fix (s/neomuttrc/gitconfig/).) > > I pushed a docs update an hour ago. Updating the docs...

v2 changes: - Call a gpgme function to get the algo string. - Use a format similar to gpg-agent(1): `"%s key, ID %s\n", algo, keyid` - Use `"?"` for an...

Hmmm, interesting thing: If the recipient is hidden (which I've tested by manually editing a real message, first decrypting it with with gpg(1), editing a few things, then re-encrypting it...

> > I like that behavior for now. > > Yeah, it looks good. > > A possible alternative is > > ``` > Recipient: RSA key, ID [hidden] >...

> A quick look at the crash (it's late here)... I see: > > ``` > (gdb) p *state > $2 = {fp_in = 0x615000016600, fp_out = 0x0, prefix =...