changeset: 6561:6034900d1636 user: Kevin McCarthy <ke...@8t8.us> date: Wed Mar 02 15:08:49 2016 -0800 link: http://dev.mutt.org/hg/mutt/rev/6034900d1636
Add hard redraw for the gpgme application/pgp handler. Will Yardley reported display artifacts and keyboard issues after decrypting a traditional pgp message using gpgme. It turns out the gpgpme code path was missing a hard_redraw() to repaint the screen after pinentry. changeset: 6562:8e77637a1a69 user: Kevin McCarthy <ke...@8t8.us> date: Wed Mar 02 15:08:54 2016 -0800 link: http://dev.mutt.org/hg/mutt/rev/8e77637a1a69 Document that GPGME doesn't support creating inline PGP messages. diffs (34 lines): diff -r d11b6776532f -r 8e77637a1a69 crypt-gpgme.c --- a/crypt-gpgme.c Sun Feb 28 19:42:40 2016 -0800 +++ b/crypt-gpgme.c Wed Mar 02 15:08:54 2016 -0800 @@ -2431,6 +2431,7 @@ NULL, plaintext); } } + mutt_need_hard_redraw (); if (err) { diff -r d11b6776532f -r 8e77637a1a69 init.h --- a/init.h Sun Feb 28 19:42:40 2016 -0800 +++ b/init.h Wed Mar 02 15:08:54 2016 -0800 @@ -568,6 +568,9 @@ ** S/MIME and PGP will be used instead of the classic code. Note that ** you need to set this option in .muttrc; it won't have any effect when ** used interactively. + ** .pp + ** Note that the GPGME backend does not support creating old-style inline + ** (traditional) PGP encrypted or signed messages (see $$pgp_autoinline). */ { "crypt_use_pka", DT_BOOL, R_NONE, OPTCRYPTUSEPKA, 0 }, /* @@ -1732,7 +1735,8 @@ ** This option controls whether Mutt generates old-style inline ** (traditional) PGP encrypted or signed messages under certain ** circumstances. This can be overridden by use of the pgp menu, - ** when inline is not required. + ** when inline is not required. The GPGME backend does not support + ** this option. ** .pp ** Note that Mutt might automatically use PGP/MIME for messages ** which consist of more than a single MIME part. Mutt can be
