From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Handling window resizing
Date: Thu, 21 May 2009 08:22:55 -0700 [thread overview]
Message-ID: <1242919028-sup-7847@entry> (raw)
In-Reply-To: <1242868891-sup-4321@ptoseis>
Reformatted excerpts from Henri Ducrocq's message of 2009-05-20:
> I tried to do it myself, first by checking for Ncurses::KEY_RESIZE in
> nonblocking_getch in buffer.rb (couldn't work because of the
> IO.select), then slightly less unsuccessfully by catching the WINCH
> event, but it looks like the signal isn't emitted in a completely
> consistent manner every time I resize the window.
>
> Any advice William?
Sadly no. There have been various attempts, by myself and others to trap
sigwinch (see e.g.
http://www.nabble.com/The-recent-patch-"redraw-screen-upon-sigwinch"-td22662878.html
which is referencing commit 9bc61b52f1a4fb3492e3799240815ed0c2a7b67f)
and to handle Ncurses::KEY_RESIZE, but something always seems screwey.
A free copy of Sup to anyone who figures this out.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-05-21 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <391beaa80905201334y4c1832adp161bb28d52f08e1@mail.gmail.com>
2009-05-21 1:31 ` Henri Ducrocq
2009-05-21 15:22 ` William Morgan [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=1242919028-sup-7847@entry \
--to=wmorgan-sup@masanjin.net \
/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