From: benoit.pierre@gmail.com (Benoît PIERRE)
Subject: [sup-talk] [PATCH] Restore keypad mode after we force ncurses to refresh the whole screen.
Date: Sat, 15 Aug 2009 01:08:48 +0200 [thread overview]
Message-ID: <1250291137-sup-2796@localdomain> (raw)
In-Reply-To: <1250289386-sup-7331@localdomain>
This also happen to fix a regression after a call to run-mailcap, since
for some reason a screen resize event is triggered when we get control
back...
---
lib/sup/buffer.rb | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/lib/sup/buffer.rb b/lib/sup/buffer.rb
index b3a256f..09281e9 100644
--- a/lib/sup/buffer.rb
+++ b/lib/sup/buffer.rb
@@ -270,6 +270,7 @@ EOS
## this magic makes Ncurses get the new size of the screen
Ncurses.endwin
+ Ncurses.stdscr.keypad 1
Ncurses.refresh
@sigwinch_mutex.synchronize { @sigwinch_happened = false }
Redwood::log "new screen size is #{Ncurses.rows} x #{Ncurses.cols}"
--
1.6.3.3
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090815/a67dfe70/attachment.bin>
next prev parent reply other threads:[~2009-08-14 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 15:23 [sup-talk] [PATCH] run-mailcap fix Benoît PIERRE
2009-08-11 20:28 ` William Morgan
2009-08-11 22:09 ` [sup-talk] [PATCH run-mailcap 1/2] Don't redirect stderr to /dev/null when calling run-mailcap Benoît PIERRE
2009-08-11 22:09 ` [sup-talk] [PATCH run-mailcap 2/2] Use BufferManager.shell_out to call run-mailcap instead of system Benoît PIERRE
2009-08-14 20:17 ` William Morgan
2009-08-14 22:37 ` Benoît PIERRE
2009-08-14 23:08 ` Benoît PIERRE [this message]
2009-08-16 22:00 ` [sup-talk] [PATCH] Restore keypad mode after we force ncurses to refresh the whole screen William Morgan
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=1250291137-sup-2796@localdomain \
--to=benoit.pierre@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