On Tue, Feb 16, 2016 at 11:43:16PM -0800, Will Yardley wrote: > On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote: > > On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote: > > > (without passphrase already cached by GPG), use 'limit' to find an > > > encrypted, *traditional* (not pgp-MIME) message in a folder. In some > > > cases, not completely reproducible, I then only see the 'S' in the index > > > lines that show up (when $pager_index_lines is set), and I see artifacts > > > of the pinentry page, sometimes sticking around for a while. The > > > screenshot here should show the behavior. > > > > > > Additionally, after this problem comes up, the up arrow in the 'limit' > > > pattern doesn't work (I get, e.g., [A for up-arrow), though I can still > > > type in there Ok. > > > > Just to help me track this: do you have $pgp_auto_decode set, or are you > > typing Esc-P inside the pager? It sounds like we need to trigger a hard > > redraw (which also turns keypad back on) on whatever path this is > > following. > > I don't have $pgp_auto_decode set, but because the messages were created > via mutt (with older GPG and $pgp_create_traditional), there's an > x-header, so I don't have to explicitly hit esc-p. > > > Also, does this only happen when you limit? > > It seemed to be easier to reproduce that way, I'll try it the other way > with some non-pgp-MIME messages.
After tracing through, it does turn out the GPGME code was missing a hard redraw call for application/pgp handling. I've added this and pushed it up. It should take care of the artifact and keyboard issues. Please let me know if it does not. I also added a note to the $pgp_autoinline and $crypt_use_gpgme options about gpgme not supporting creating inline pgp. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
