bug-ncurses
[Top][All Lists]
Advanced

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

Terminal echo


From: olafBuddenhagen
Subject: Terminal echo
Date: Tue, 1 Apr 2003 22:02:47 +0200
User-agent: Mutt/1.5.3i

Hi,

There is a problem in conjuction with Readline: When temporary leaving
curses fullscreen mode, invoking readline, and reactivating curses mode,
the terminal settings somehow get wrong, and typed characters are echoed
to the screen. (This is *not* curses generated echo, but terminal echo.)
I've attached a simple test program demonstrating this.

The problem appeared in 5.3; it worked fine up to 5.2. I tried to find
the reason, but I wasn't able do track down any obvious change between
those versions which might explain that...

Note that while nobody seems to have noticed the problem before (maybe
no other programs are using curses and readline alternating...), I
consider it a critical bug -- my own program (netrik) is really unusable
with that, and I do not have any idea how to work this around. (Except
for disabling readline support alltogether and using fgets()...)

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

-Olaf-

PS. Last time I send a bug report to address@hidden I never got any
answer. Only when browsing the changelog I realized that it actually got
through and the problem was fixed...

-- 
Don't buy away your freedom -- GNU/Linux

Attachment: curses-bug.c
Description: Text Data


reply via email to

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