[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Terminal echo

From: Thomas Dickey
Subject: Re: Terminal echo
Date: Sat, 5 Apr 2003 17:56:59 -0500
User-agent: Mutt/1.3.27i

On Sat, Apr 05, 2003 at 06:56:39PM +0200, address@hidden wrote:
> > > BTW, there is another (not new) problem with readline: Ncurses' default
> > > SIGWINCH handler doesn't work anymore after using readline, although
> > > readline seems to restore it correctly... (Restoring manually doesn't
> > > help either.) I've no idea what goes wrong here; I didn't find any
> > > reason although I studied the sources of both readline and ncurses. (Who
> > > knows, maybe it's actually a problem of the OS signal handling... Maybe
> > > someone should test it on something different than GNU/Linux2.4.) This
> > > problem isn't that critical however, as it can be avoided by using an
> > > own signal handler, and also SIGWINCH handling really isn't that
> > > important...
> > 
> > with netrik, or a simpler application?
> I've now created a simplified test case for this also; see attachment.

I can reproduce this (but don't know the answer yet, either).  strace seems
to show that readline is restoring the signal handler, but ncurses sees
that it's is interrupted (though the sigwinch is registered as well).

I'm too short of time this weekend to delve into it, but do have the echoing
problem fixed.

Thomas E. Dickey <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]