Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Sven Moritz Hallberg <sm@khjk.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] curses pinentry woes (still)
Date: Sun, 07 Feb 2010 20:10:04 +0100	[thread overview]
Message-ID: <1265569783-sup-1789@khjk.org> (raw)

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


             reply	other threads:[~2010-02-07 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-07 19:10 Sven Moritz Hallberg [this message]
2010-02-07 20:25 ` Michael Stapelberg
2010-02-18 18:10   ` Michael Stapelberg
2010-02-18 18:35     ` Sven Schober
2010-02-19  3:29       ` Michael Stapelberg
2010-02-19 10:30         ` Sven Schober
2010-02-21 11:13           ` Sven Schober

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1265569783-sup-1789@khjk.org \
    --to=sm@khjk.org \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox