Alejandro Colomar

Something I just discovered: one needs to explicitly unignore `From` and a few other header fields. They are ignored by default. Not a big deal, though. I ended up using...

v8 changes: - Protect the date, just as mutt(1) does. It is also recommended by the RFC drafts I read. ``` $ git range-diff devel/security gh/protect protect 1: 472a12767 =...

v8b (by @flatcap ) changes: - Rebase ``` $ git range-diff devel/security..protect neomutt/devel/security..gh/protect 1: 472a12767 = 1: 4b9fa065c ncrypt/crypt.c: Protect address lists in header fields 2: 8ef02901b = 2: 6cbbed78d...

v8c changes: - sort(1) prototypes [@flatcap ] - Add Doxygen comments [@flatcap ] - Expand commit messages ``` $ git range-diff devel/security gh/protect protect 1: 4b9fa065c = 1: 4b9fa065c ncrypt/crypt.c:...

v9 changes: - clang-format [@flatcap ] ``` $ git range-diff --creation-factor=99 devel/security gh/protect protect 1: 4b9fa065c = 1: 4b9fa065c ncrypt/crypt.c: Protect address lists in header fields 2: cc9b518ee = 2:...

v10 changes: - Add tests for mutt_list_copy_tail(). ``` $ git range-diff devel/security gh/protect protect 1: 4b9fa065c = 1: 4b9fa065c ncrypt/crypt.c: Protect address lists in header fields 2: cc9b518ee = 2:...

v11 changes: - Fix tests ``` $ git range-diff devel/security gh/protect protect 1: 4b9fa065c = 1: 4b9fa065c ncrypt/crypt.c: Protect address lists in header fields 2: cc9b518ee = 2: cc9b518ee list:...

v12 changes: - Fix tests ``` $ git range-diff devel/security gh/protect protect 1: 4b9fa065c = 1: 4b9fa065c ncrypt/crypt.c: Protect address lists in header fields 2: cc9b518ee = 2: cc9b518ee list:...

@flatcap Can you please check what's wrong with the tests? is failing, but I don't see exactly why.

Maybe you want to read grotty(1): ``` Legacy output format The -c option tells grotty to use an output format compatible with paper terminals, like the Teletype machines for which...