From mboxrd@z Thu Jan  1 00:00:00 1970
From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Date: Wed, 05 Aug 2009 22:25:49 +0200
Subject: [sup-talk] sup ignoring SIGTERM?
In-Reply-To: <1249502171-sup-8079@masanjin.net>
References: <1249481294-sup-9967@chistera.yi.org>
	<1249502171-sup-8079@masanjin.net>
Message-ID: <1249503870-sup-1415@ausone.home>

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