Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] sup and gpg-agent
Date: Tue, 22 Jan 2008 09:22:32 +0100	[thread overview]
Message-ID: <1200990103-sup-9355@ausone.local> (raw)
In-Reply-To: <1200985659-sup-8098@south>

Excerpts from William Morgan's message of Tue Jan 22 08:17:01 +0100 2008:
> Reformatted excerpts from nicolas.pouillard's message of 2008-01-21:
> > After  giving  to  gpg  my  pass  phrase (ncurses based), sup seems
> > completely lost, arrow bindings no longer works... and I have to
> > restart sup.
> 
> Assuming you're talking about pinentry-curses, I see the same behavior
> too. I'm not sure how to fix it, or if it's even possible. It might be
> that pinentry-curses isn't restoring the console state to how it found
> it, it might be that Sup is supposed to be doing something different
> (but what? It's not notified when pinentry-curses is called). Someone
> who's a curses expert might know.
> 
> My workaround was to install pinentry-gtk. :)

You're right, this *workaround* works for me too :)

-- 
Nicolas Pouillard aka Ertai
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080122/ad8bfe3e/attachment-0001.bin 


      reply	other threads:[~2008-01-22  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 16:15 Nicolas Pouillard
2008-01-22  7:17 ` William Morgan
2008-01-22  8:22   ` Nicolas Pouillard [this message]

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=1200990103-sup-9355@ausone.local \
    --to=nicolas.pouillard@gmail.com \
    /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