From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.213.28.69 with SMTP id l5cs31430ebc; Sun, 7 Feb 2010 11:40:29 -0800 (PST) Received: by 10.224.27.30 with SMTP id g30mr2083446qac.6.1265571628774; Sun, 07 Feb 2010 11:40:28 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 5si7177437qwg.28.2010.02.07.11.40.28; Sun, 07 Feb 2010 11:40:28 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 450551588077; Sun, 7 Feb 2010 14:40:28 -0500 (EST) X-Greylist: delayed 1317 seconds by postgrey-1.31 at rubyforge.org; Sun, 07 Feb 2010 14:32:05 EST Received: from atomzentrale.khjk.org (atomzentrale.khjk.org [212.12.50.211]) by rubyforge.org (Postfix) with ESMTP id F2D593C803E for ; Sun, 7 Feb 2010 14:32:05 -0500 (EST) Received: from pesco by atomzentrale.khjk.org with local (Exim 4.63) (envelope-from ) id 1NeCWC-0007ku-93 for sup-talk@rubyforge.org; Sun, 07 Feb 2010 20:10:04 +0100 From: Sven Moritz Hallberg To: sup-talk Date: Sun, 07 Feb 2010 20:10:04 +0100 Message-Id: <1265569783-sup-1789@khjk.org> User-Agent: Sup/0.10.2 Subject: [sup-talk] curses pinentry woes (still) X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Hi List, I see there have been posts about this before, the last from Oct 2009. Whenever gpg-agent starts pinentry-curses with sup running, the interface gets "messed up". Unfortunately, I'm still experiencing such a problem with sup version 0.10.2. Specifically, when the pinentry screen appears and I press the first key, sup suddenly reappears, the cursor moves to the bottom right corner and the passphrase stars start appearing there, wrapping over to the left. When I press Enter, pinentry reappears and almost always states "wrong passphrase", so I presume something about the input must get mangled somewhere. Now when I try again, everything looks as it should (in pinentry) and the passphrase is accepted. However, after that, sup does not behave normally. The screen does not update and commands only seem to be recognized if Enter is pressed afterwards. So I have to press "q Enter" and restart. On a related note, it asks for the passphrase periodically. Does it require gpg calls every time it polls for new messages? Is there a way to stop that? Regards, Sven _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk