On Sat, Dec 26, 2015 at 06:32:03AM +0100, Matthias Apitz wrote: > El día Friday, December 25, 2015 a las 06:57:05PM -0800, Ian Zimmerman > escribió: > > > On 2015-12-25 08:11 +0100, Matthias Apitz wrote: > > > > > In the mutt' terminal (a uRxvt) the screen is a bit mangled: > > > ... > > > i.e. the \n at the end of each line is not interpreted anymore as \n+\r; > > > also the ENTER key sends only a \r to the STDIN of pinentry which is not > > > understood either as the end of the keyed-in passphrase; it took me some > > > time to figure out that I have to use Ctrl-j to end the passphrase; with > > > this all is fine, apart of the mangeled message above; > > > > Looks like raw vs. cooked mode issue. Should be fixable with stty. > > Ofc, but I think, this must be done inside mutt itsef, which hands over > the tty in this state;
Mutt uses cbreak mode, but doesn't toggle raw/cooked mode anywhere as far as I can tell. In this case, the "Invoking PGP..." message is output before starting to display an encrypted message. It's generated by a mvaddstr() and refresh(). For gpgme, mutt is just making gpgme function calls, e.g. gpgme_op_decrypt_verify(), and then setting a flag to do a redraw afterwards. I don't see the code doing anything much different between decrypt/verify and signing. Werner, can you see anything different between gpgme_op_decrypt_verify() and gpgme_op_sign() and how they invoke pinentry if needed? -- 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
