STATUS: not merged COMMENT: maybe it is misconfigured terminal and/or Pine bug - in such case it wont be reasonable to fix it by PinePGP changes; anybody had or have same problems? Date: Thu, 4 Oct 2001 14:54:41 -0400 (EDT) From: mike ledoux To: Subject: PinePGP Patches -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've made the attached (trivial) patch to PinePGP 0.16.0 for your consideration. This patch modifies PinePGP to use Pine's _TMPFILE_ token instead of stdin/stdout for Encrypt/Decrypt/Sign/Verify operations. This allows me to clear the 'background' screen that the gpg output shows up in, to make it much easier to read (I had a problem where the gpg output was sometimes mixed on the terminal with whatever text was on-screen when I started pine, making it difficult to determine what was going on). I've tested this on a couple of different systems, for a couple of different users, but only with GPG 1.0.6. So, IWFM, YMMV. :) - -- mwl+gnupg@alumni.unh.edu OpenPGP KeyID 0x57C3430B Holder of Past Knowledge CS, O- Key fingerprint = AA02 86F6 FE1B 552C BB86 1D85 E6B8 1D1C 57C3 430B "If at first you don't succeed, destroy all evidence that you tried." -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7vLB15rgdHFfDQwsRAmVnAJ9z6+DTdSEoRL57UjkNsiXcUWwMBwCg4T/6 rcW0MAVLTciezxOSgDtKMDs= =G0gC -----END PGP SIGNATURE-----