jba@harald.ruc.dk (Jan B. Andersen) (12/23/89)
Here at RUC we have a MV with AOS/VS TCP/IP and also an Aviion
workstation. Unfortunately, the terminfo supplied with the
workstation for the DASHER terminal won't work with the terminal
in DG mode (it assumes ANSI). I have made the following terminfo
which works for two cases: DASHER connected to MV running TELNET
and DASHER on a Communications Server (terminalserver):
TERM=d200-vs TERM=d200-cs
+--------+ +--------+
| DASHER | | DASHER |
+--------+ +--------+
| |
| |
+--------+ +--------+ +---------+
| AOS/VS | | BRIDGE | | Aviion |
| TELNET | | CS/200 | | telnetd |
+--------+ +--------+ +---------+
| | |
| | |
============================================
Comments, questions and/or fixes are most welcome!
--
/| / Postmaster@RUC.dk /^^^\ .----------------.
/ | / DG-passer@RUC.dk { o_o } | SIMULA does it |
/--|/ jba@dat.RUC.dk \ o / --> | with CLASS |
`--' ' rucjb@os1100.uni-c.dk --mm---mm-- `----------------'
-------------------[cut here]------------------------------
#
# ruc: DATA GENERAL terminals as used on Roskilde University Center
#
# The following description of the Data General DASHER D200 terminal
# was generated using infocmp(1).
#
d200|Data General DASHER D200,
am, bw, msgr,
cols#80, lines#24,
bel=^G, blink=^N, bold=^^D^T, clear=\f, cr=\r,
cub1=^Y, cud1=^Z, cuf1=^X, cup=^P%p2%c%p1%c, cuu1=^W,
dim=^\, el=^K, home=^P\200\200, ind=\n, is1=^R^C,
kHOM=^^\b, kLFT=^^^Y, kRIT=^^^X, ka1=^^\\, ka3=^^],
kc1=^^\^, kc3=^^_, kclr=\f, kcub1=^Y, kcud1=^Z,
kcuf1=^X, kcuu1=^W, kel=^K, kf1=^^q, kf10=^^z,
kf11=^^{, kf12=^^|, kf13=^^}, kf14=^^~, kf15=^^p,
kf16=^^a, kf17=^^b, kf18=^^c, kf19=^^d, kf2=^^r,
kf20=^^e, kf21=^^f, kf22=^^g, kf23=^^h, kf24=^^i,
kf25=^^j, kf26=^^k, kf27=^^l, kf28=^^m, kf29=^^n,
kf3=^^s, kf30=^^`, kf31=^^1, kf32=^^2, kf33=^^3,
kf34=^^4, kf35=^^5, kf36=^^6, kf37=^^7, kf38=^^8,
kf39=^^9, kf4=^^t, kf40=^^:, kf41=^^;, kf42=^^<,
kf43=^^=, kf44=^^>, kf45=^^0, kf46=^^!, kf47=^^",
kf48=^^#, kf49=^^$, kf5=^^u, kf50=^^%, kf51=^^&,
kf52=^^', kf53=^^(, kf54=^^), kf55=^^*, kf56=^^+,
kf57=^^\,, kf58=^^-, kf59=^^., kf6=^^v, kf60=^^\s,
kf7=^^w, kf8=^^x, kf9=^^y, khome=\b, ll=^P\200^W,
mc0=^Q, nel=\n, rev=^^D, rmso=^^E^], rmul=^U,
sgr=^^%?%p1%p3%|%p6%|%tD%eE%;%?%p2%p6%|%t^T%e^U%;%?%p4%t^N%e^O%;%?%p1%p5%|%t^\%e^]%;,
sgr0=^O^U^]^^E, smso=^^D^\, smul=^T,
# Info:
# DASHER D200 terminal used with MV running AOS/VS TCP/IP.
#
# Some kind of optimization in curses(3) causes problem when
# scrolling. The problem is most evident when scrolling very
# short lines e.g. just a comment (#). By disabling cub1,
# curses(3) will not use the errornous sequence {cud1,ind,cub1,cup1}
# (ind puts cursor at column 0, cub1 then moves cursor to column 79
# on the previous line). Instead {cud1,ind,cr,cup1} will be used.
# However, having no cub1 means, that any cursor-left movement
# causes some light flickering when the cursor goes {cr,cuf1....}.
#
# How and why this affects cup I don't know, but cup doesn't work
# reliably without cub1, so I have disabled cup too, without noticing
# any slowdown in screen updates.
#
# Jan B. Andersen <jba@dat.ruc.dk>
# Computer Science Department
# Roskilde University Center
#
d200-vs|dasher-vs|Data General DASHER D200,
cub1@,
cup@,
use=d200,
# Info:
# DASHER D200 terminal used with Bridge TCP/IP Communications Server
#
# Appearently we get a full 8 bit communications path when using the
# terminal server. This causes some problems when curses(3) tries to
# output a string containing NULL's by sending the NULL as \0200,
# hoping that the receiver strips the high bit. Disabling ll and
# redefining home takes care of that problem. Now, could someone
# please tell me how to get the NEWLINE key to work in the shell?
#
# Jan B. Andersen <jba@dat.ruc.dk>
#
d200-cs|dasher-cs|dasher|Data General DASHER 200,
ll@,
home=\b,
use=d200-vs,