Gary Jennejohn schrieb am 2009-10-23: > On Fri, 23 Oct 2009 12:58:43 +0400 > pluknet <pluk...@gmail.com> wrote:
> > 2009/10/23 Antony Mawer <li...@mawer.org>: > > > On Fri, Oct 23, 2009 at 1:35 PM, Alexander Best > > > <alexbes...@math.uni-muenster.de> wrote: > > >> hi everyone, > > >> together with hugh mahon (the author of ee) i've been trying to > > >> fix a nasty > > >> bug in ee. for some reason ee exits (not crashes) and leaves the > > >> console > > >> corrupted when receiving SIGWINCH (`killall -SIGWINCH ee` should > > >> exit all > > >> running ee instances). > > > I noticed this the other day when working on a new 8.0-RC1 > > > system... > > > in my case I was using putty (Windows ssh client) to access the > > > system > > > and maximised the window I had ee running in, and noticed ee just > > > dumped me straight to the prompt. > > > I am wondering if this has anything to do with the new tty > > > subsystem > > > in 8.0, as this wasn't a problem I've experienced before under > > > 7.x... > > No, that's a regression appeared in (FreeBSD'ish? version of) ee > > 1.5.0. > SIGWINCH is handled in new_curse.c, but it's not being > compiled/linked. > --- > Gary Jennejohn i just tried building ee under linux without using new_curse.c and linking the executable against ncurses. running the binary is showing the same problems with SIGWINCH. so if this is in fact caused by a ncurses bug the bug appears in linux ncurses too. alex _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
