Dear Tru64 admins,
I ask your info about a "tic" misbehaviour:
I access an Alpha server (running Tru64 4.0D) remotely from an
Alpha Linux workstation (running SuSE 7.0 AXP, kernel 2.2.16).
The "TERM" setting on the Linux box is "xterm-color" (new in
7.0, AFAIR).
As the Tru64 terminfo definitions do not provide for that terminal
name, I have to bridge the gap.
To do that in a "clean" way, I created a private terminfo source
("/usr/local/terminfo/sql.ti", to allow more such things)
and put a small entry there:
xterm-color|xterm terminal emulator with colours,
colors#8, use=xterm,
(I know that the Tru64 definition already has colours defined
for an "xterm", but I thought this to be the "clean" way in
preparing for OS upgrades - to keep the original source unchanged.
I also know that I could reach the effect by chenging the "TERM"
value, but I preferred this way - matter of personal taste.)
According to the "man" page, "tic" will process a "use=" directive
from the current file, then read the binary entry from
"/usr/share/lib/terminfo".
On my machine, however, "tic" simply gives me a message
Cannot find term xterm
even though that clearly exists as a binary description.
(environment: "TERM=xterm", "TERMINFO" not set;
"vi" and "man" work - which they do not if
"TERM=xterm-color" for lack of definition.)
I know that I could copy the whole description or use some other
bypass, but I still would prefer my "local" change to refer
to the "current official" definition without copying.
Do you have any hints how I can make "tic" use an existing
binary description to process the "use=" directive ?
Thank you all,
Joerg Bruehe
--
Joerg Bruehe, SQL Datenbanksysteme GmbH, Berlin, Germany
(speaking only for himself)
mailto: joerg_at_sql.de
Received on Thu Mar 08 2001 - 11:38:58 NZDT