From: Rich Lane <rlane@club.cc.cmu.edu>
To: Michael Stapelberg <michael+sup@stapelberg.de>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Bugfix: Don\xe2\x80\x99t call Ncurses.getch when in shell\x96out mode
Date: Sat, 27 Feb 2010 03:23:39 -0500 [thread overview]
Message-ID: <1267258772-sup-9178@zyrg.net> (raw)
In-Reply-To: <1266549876-sup-2041@midna.zekjur.net>
Excerpts from Michael Stapelberg's message of 2010-02-18 22:26:37 -0500:
> Hi,
>
> (at least for me) the attached patch finally fixes the pinentry-ncurses
> problems we were still having (as soon as you press a key, the screen is
> garbage).
>
> To quote the commit message:
>
> Previously, when using threads, Ncurses.getch was called while
> the gpg pinentry was running (as an example of using the shell_out
> method). Now, the Ncurses mutex will be used to wait until shell_out
> mode is finished.
>
> Please have a look if this patch is working for you and merge it for the next
> release.
>
> Best regards,
> Michael
What's the reason for passing the BufferManager singleton as an
argument?
What does "drop the input" mean?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-02-27 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 3:26 [sup-devel] [PATCH] Bugfix: Don’t call Ncurses.getch when in shell�out mode Michael Stapelberg
2010-02-27 8:23 ` Rich Lane [this message]
2010-02-27 12:48 ` [sup-devel] [PATCH] Bugfix: Don\xe2\x80\x99t call Ncurses.getch when in shell\x96out mode Michael Stapelberg
2010-02-27 18:12 ` Rich Lane
2010-02-27 19:00 ` [sup-devel] [PATCH] Bugfix: Don't call Ncurses.getch when in shell-out mode William Morgan
2010-02-27 19:03 ` Rich Lane
2010-02-27 19:29 ` William Morgan
2010-02-27 19:27 ` [sup-devel] [PATCH] Bugfix: Don\xe2\x80\x99t call Ncurses.getch when in shell\x96out mode Michael Stapelberg
2010-02-27 20:14 ` Rich Lane
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=1267258772-sup-9178@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=michael+sup@stapelberg.de \
--cc=sup-devel@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