From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Odd key bug
Date: Mon, 27 Jul 2009 14:30:46 -0400 [thread overview]
Message-ID: <1248719342-sup-9126@javelin> (raw)
In-Reply-To: <1248718344-sup-1931@javelin>
I currently suspect that if I send a null character to the stdscr
(which would require bin/sup to be rewritten a little to make stdscr
globally available) it would serve as a decent workaround. I don't
actually know how global variables work in Ruby.
(Basically, add stdscr.keypad(0) when we return from the external shell.)
Cheers,
Edward
next prev parent reply other threads:[~2009-07-27 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:13 Edward Z. Yang
2009-07-27 17:27 ` Alex Vandiver
2009-07-27 17:52 ` Ben Walton
2009-07-27 17:33 ` William Morgan
2009-07-27 18:13 ` Edward Z. Yang
2009-07-27 18:30 ` Edward Z. Yang [this message]
2009-07-27 19:15 ` Edward Z. Yang
2009-07-28 15:17 ` William Morgan
2009-07-28 15:31 ` Ben Walton
2009-07-27 18:47 ` Tarko Tikan
2009-07-27 20:11 ` Andrew Pimlott
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=1248719342-sup-9126@javelin \
--to=ezyang@mit.edu \
/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