On Wed, Mar 02, 2016 at 03:17:25PM -0800, Kevin J. McCarthy wrote: > 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:
> > > > 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. > 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. Thanks so much for the hard work on this. Minor issues, I know, but they've been driving me nuts since I switched to GPG 2 / gpgme. w
