From: Sven Schober <sven.schober@uni-ulm.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] pinentry-curses messes up sup
Date: Tue, 13 Oct 2009 10:13:53 +0200 [thread overview]
Message-ID: <1255421626-sup-4525@hysbald> (raw)
In-Reply-To: <1255292709-sup-2216@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]
Excerpts from William Morgan's message of Sun Oct 11 22:25:33 +0200 2009:
> Reformatted excerpts from Sven Schober's message of 2009-10-10:
> > As that thread is rather old, i would like to now if there's been some
> > development on this? Are there any console alternatives to
> > pinentry-curses?
>
> I think I've fixed this in git next. Please try that.
Works like a charm :) Thanks!
--
Sven Schober, sven.schober@uni-ulm.de |UNI ULM
http://www-vs.informatik.uni-ulm.de/dept/staff/schober/ |DISTRIBUTED
Room O27-346, Phone: +49-731-5024146 [+49-179-5060182] |SYSTEMS LAB
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-13 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 12:01 Sven Schober
2009-10-11 20:25 ` William Morgan
2009-10-13 8:13 ` Sven Schober [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=1255421626-sup-4525@hysbald \
--to=sven.schober@uni-ulm.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