Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup ignoring SIGTERM?
Date: Wed, 05 Aug 2009 14:24:49 -0700	[thread overview]
Message-ID: <1249507336-sup-7887@masanjin.net> (raw)
In-Reply-To: <1249503870-sup-1415@ausone.home>

Reformatted excerpts from Nicolas Pouillard's message of 2009-08-05:
> With the ncurses-fixes branch (even with the last patch), when I
> launch sup I get a blank screen (with the status bar saying "Searching
> for threads...".

Dammit. I see that too, on some computers. The problem is that
Ncurses.getch is actually blocking the background threads from working.
(You can tell because threads will start loading when you press lots of
keys.)

I've unmerged the branch from next for the time being.

The problem is the removal of the select() in nonblocking_getch
(buffer.rb circa line 25). With it in, resizes don't work right. With it
removed, background threads are blocked on some computers. Not sure what
makes the difference. Sigh...
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-08-05 21:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 14:09 Adeodato Simó
2009-08-05 20:03 ` William Morgan
2009-08-05 20:25   ` Nicolas Pouillard
2009-08-05 21:24     ` William Morgan [this message]
2009-08-06 17:53       ` William Morgan
2009-08-06 18:09         ` Nicolas Pouillard
2009-08-06 23:56         ` Ben Walton
2009-08-05 20:35   ` Ben Walton
2009-08-05 21:28   ` Edward Z. Yang
2009-08-06 18:37   ` Adeodato Simó
2009-08-07  1:38     ` William Morgan
2009-08-07 10:31       ` Adeodato Simó
2009-08-07 16:40         ` Rich Lane
2009-08-08  9:23           ` Adeodato Simó

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=1249507336-sup-7887@masanjin.net \
    --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