Linux terminfo or xterm problem

[J Sadler]

Hi all

When I use an xterm started on a HP-UX or Solaris host and ssh to a linux box, underline and inverse video are not terminated properly.

ie: doing a man on man give underlines that can span pages of output. Or using more cause inverse video for all output after the first page.

I'm assuming it's a issue with Linux as it happens from both HPUX and Solaris. Does the terminfo/cap need fixed or ????

Thanks
J Sadler

[Steven E. Protter]

Try a few different TERM variables.

TERM=ansi
TERM=vt100
TERM=vt200

You might get different behaviors and therefore a clue to the progblem.

I have been vexed trying to make neterm work with Linux and not screw with color configuration when you do a ll or ls command.

The best I've done so far is download a ssh terminal program named putty

That's not going to help with this, just venting.

SEP

[Balaji N]

hi,
read a post on itrc some time back (dont remember exact details) which provided a possible solution to this problem.

the idea was to use infocmp / tic / untic to decompile the terminfo file of linux and take it to a hp box and compile it there. and then use the terminal type as linux.

may be you can read the man pages and give a try. and post the solution book. (and i will not forget to do a book mark :-) )

hth
-balaji

[Bill Hassell]

As has been true for more than 2 decades, terminals are not standardized and the way in which one terminal (or wannabe emulator) handles video enhancements is often quite different than another. The oft-misused term VT100 is so horribly emulated by various programs, that the opsystem is usually blamed for the problems when it is simply the way the emulator works with the rules defined by the TERM variable.

In HP-UX, a terminfo database of hundreds of terminal characteristics files are kept in /usr/lib/terminfo. These files are in binary format but can be read with untic as in: untic vt100

The man page for terminfo lists all the Curses library parameters that may be called from application programs. Earlt code writers found that some terminals would start an enhancement (ie, underline) and the next CR or LF character would turn it off. But other terminals needed an End-Enhancment or End-all-enhancments escape sequence to stop the underlining.

So if a program is written to properly terminate the sequence, yet it does not work then the terminfo entry is incorrect. There will be an smul entry for underlining, but there should also be rmul to exit underlining as well as sgr0 to exit all enhancment modes.

[Runar Jørgensen]

Greetings!

Might just not only be terminfo/termcap. I've
experienced some really wierd stuff when bash is invovled.

* What are the shells you're using?
* Can you do a "stty -a" on both ends?
* Are you sure you're using xterm and not dtterm on Solaris/HP-UX?

Regards,
Runar J??rgensen