bug-ncurses
[Top][All Lists]
Advanced

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

Re: Terminal echo


From: Thomas Dickey
Subject: Re: Terminal echo
Date: Tue, 1 Apr 2003 18:51:11 -0500
User-agent: Mutt/1.2.5i

On Tue, Apr 01, 2003 at 10:02:47PM +0200, address@hidden wrote:
> 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.

I'll take a look at it.  Nothing comes to mind that would be a problem.
 
> 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()...)

there aren't many - I recall some years ago someone reported problems in
initialization, but haven't noticed anything recently.  I had in mind
recently that someone once told me that readline had enough hooks to allow
ncurses to substitute for the display function of readline, but on investigation
found that was not so.  (Otherwise I would have modified test/filter.c to
do this, eliminating an faq). 
 
> 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?
 
> -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...

I usually reply (unless it's a how-to question that gets a response from
someone else).

But sometimes I reply only to the list, not remembering if the person was
subscribed.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net




reply via email to

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