Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] sup ignoring SIGTERM?
Date: Wed, 05 Aug 2009 22:25:49 +0200	[thread overview]
Message-ID: <1249503870-sup-1415@ausone.home> (raw)
In-Reply-To: <1249502171-sup-8079@masanjin.net>

Excerpts from William Morgan's message of Wed Aug 05 22:03:09 +0200 2009:
> Reformatted excerpts from Adeodato Sim?'s message of 2009-08-05:
> > it is my impression that sup is ignoring SIGTERM, whereas I would be
> > expecting for sup to clean up (including removal of the lock file) and
> > exit normally upon receiving this signal.
> 
> Good point. I've fixed that in branch ncurses-fixes, which I've merged
> into next. Let me know if it works for you.
> 
> I'm also happy to report that I've finally managed to get Sup to deal
> with screen resizes, which, oddly enough, was a related problem. Go me!
> Steps closer to curses-induced insanity: 4!
> 
> Available on next or ncurses-fixes branches.

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...".

-- 
Nicolas Pouillard
http://nicolaspouillard.fr


  reply	other threads:[~2009-08-05 20:25 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 [this message]
2009-08-05 21:24     ` William Morgan
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=1249503870-sup-1415@ausone.home \
    --to=nicolas.pouillard@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