[Top][All Lists]

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

Re: [Lynx-dev] Lynx behaviour in VT320 terminals

From: Thomas Dickey
Subject: Re: [Lynx-dev] Lynx behaviour in VT320 terminals
Date: Sun, 27 Mar 2005 14:27:28 -0500 (EST)

On Sun, 27 Mar 2005, John Kerr Anderson wrote:

Hi Again,

OK, the actual setup is Debian 3.0 intel pc as host system, and a Dorio 10 terminal set in the computer (/etc/inittab file) as vt320. The terminal is set for the vt320 personality (default mode). It's essentially a vt510 w/different comm. ports. The keyboard on the terminal is a VT-ANSI style keyboard w/106 keys.

hmm - PC keyboard and/or not-really-vt320...

Older versions of Debian the default lynx program would not force the terminal into application keypad/cursor mode. Newer versions however do. Also, whenever I'd compile my own version of Lynx on Debian it would also force the terminal into the application keypad/cursor mode.

I can tell because when I'm not running lynx I can enter terminal setup and the checkboxes are unchecked for application keypad/cursor mode. When I start Lynx, then those fields are checked.

And when exiting, they should be unchecked. lynx doesn't know really what the terminal description says - it just tells ncurses that it wants to
use function keys, so ncurses sends out smkx (and ncurses has to believe
the terminal description as well).

I'd just like to use lynx w/the numeric keypad again :) So, I can I don't have to enter terminal setup everytime I need to use the numeric keypad. :( Thanks for the info thus far. I'm just not sure where to go from here...

It sounds as if either the $TERM is different, or the corresponding terminfo entry changed.

Another thought - some time ago - I don't recall when - Debian's package for lynx used slang. A quick check of that shows it's not setting application mode (so it's ignoring parts of the terminal description, using some hardcoded logic instead: since it does not set cursor application mode, then it shouldn't be able to read cursor keys because the strings do not match).

That's done by the terminal description.  In terminfo, that is the
smkx string, e.g.,

If you have the old system running, it's simple to get the terminal
description - just run infocmp, and its output shows all of the information. Edit the output, remove the parts you don't want, and
run tic on the file, e.g.,

        infocmp >foo
        vi foo
        tic foo

To install in the system's copy of terminfo, you have to run tic as root.

Mainly as an illustration for bash users, I made a no-application mode
entry for xterm:

xterm-noapp|xterm with cursor keys in normal mode,
        kcub1=\E[D, kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A, rmcup@,
        rmkx=\E>, smcup@, smkx=\E=, use=xterm,

You can define your own vt320-noapp in the same way, and set the inittab
to use that.

Thomas E. Dickey

reply via email to

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