curses and some terminals

dimm_coder · 04-05-2004, 03:04 AM

I have found out that different terminals (GUI mode) deal with curses apllications in different ways.
The problem is that some of them (eterm, gnome term, KDE) restore the view of the window
to the previous state after any curses application has completed. So the user is not able to see any output results. Only xterm doesn't do this.
How can I deal with this? Some terminal option should be set to prevent this?

Mohsen · 04-06-2004, 12:12 PM

I dont know why, but I think this happens as soon as endwin(). Try to chage terminal properties back to the original one without using endwin(). You may find your answer by reading the source (I coudn't fingure out the code!!)

Code:

#include <curses.priv.h>
#include <term.h>

MODULE_ID("$Id: lib_endwin.c,v 1.19 2000/12/10 02:43:27 tom Exp $")

NCURSES_EXPORT(int)
endwin(void)
{
    T((T_CALLED("endwin()")));

    if (SP) {
	SP->_endwin = TRUE;
	SP->_mouse_wrap(SP);
	_nc_screen_wrap();
	_nc_mvcur_wrap();	/* wrap up cursor addressing */
	returnCode(reset_shell_mode());
    }

    returnCode(ERR);
}

dimm_coder · 04-07-2004, 01:30 AM

Quote:

Originally posted by Mohsen
[B]I dont know why, but I think this happens as soon as endwin(). Try to chage terminal properties back to the original one without using endwin(). You may find your answer by reading the source (I coudn't fingure out the code!!)

Thank U for the answer.
Yes, if I comment out the endwin() call, the screen isn't restoring, but the terminal doesn't get the correct mode after the program ends. I was wondering mostly, because endwin() behavior on some terminals isn't compliant with documentation. Probably, endwin() use some terminal dependent code (set/restore some terminal flags). I'll take a look into sources and try to figure out.

Mohsen · 04-09-2004, 01:01 AM

You can also ask your question from ncurses maintainer at bug-ncurses@gnu.org

Mohsen · 04-09-2004, 01:05 AM

Heh, I've just found that you did it before

dimm_coder · 04-09-2004, 02:53 AM

Quote:

Originally posted by Mohsen
Heh, I've just found that you did it before

Yes, I did it

arvind_sv · 05-08-2004, 08:58 PM

Hi,

You must have got an answer from the ncurses folks already. It's not a bug.
Look at the xterm man page and search for "titeInhibit".

Also, if you haven't yet found out from them how to get the terminal emulators to do what you want them to, tell me.

Arvind

dimm_coder · 05-10-2004, 02:44 AM

Thanks, arvind, for your answer.
Well, that was a program I had to rewrite in some parts. This program used the ncurses library for achieving a coloring output.
It had some drawbacks: 1) that one with terminals I have pointed above; 2) the program may have a long output and, thus, another problem with scrolling. So I've rewrote it using the screen output with escape sequences, not using ncurses. That solved all problems.
At any rate, thanks for advice.

dimm_coder · 05-10-2004, 02:45 AM

Thanks, arvind, for your answer.
Well, that was a program I had to rewrite in some parts. This program used the ncurses library for achieving a coloring output.
It had some drawbacks: 1) that one with terminals I have pointed above; 2) the program may have a long output and, thus, another problem with scrolling. So I've rewrote it using the screen output with escape sequences, not using ncurses. That solved all problems.
At any rate, thanks for advice.

arvind_sv · 05-10-2004, 11:04 AM

You could have used the scrolling functionality of ncurses. I've been wanting to try it out.

Anyhow, glad to know that it worked out,
Arvind