From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] curses pinentry woes (still)
Date: Sun, 07 Feb 2010 21:25:57 +0100 [thread overview]
Message-ID: <1265574271-sup-5738@midna.zekjur.net> (raw)
In-Reply-To: <1265569783-sup-1789@khjk.org>
Hi Sven,
Excerpts from Sven Moritz Hallberg's message of So Feb 07 20:10:04 +0100 2010:
> 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.
I have a similar problem, though it only happens when sup has other output to
my terminal while the pinentry is running. That is, when you catch a quiet
moment (between polling intervals), you can enter your passphrase without any
problems.
I intend to fix this problem in a few weeks, if nobody does it before I do.
Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-02-07 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 19:10 Sven Moritz Hallberg
2010-02-07 20:25 ` Michael Stapelberg [this message]
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=1265574271-sup-5738@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
--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