guy@coat.com (Guy T. Schafer) (12/15/89)
To Whom It May Concern: A section of our /etc/termcap file looks like this: #---------------- vs|xterm|vs100:cr=^M:do=^J:nl=^J:bl=^G:le=^H:ho=\E[H:co#80:li#56:\ :cl=\E[H\E[2J:bs:cm=\E[%i%d;%dH:nd=\E[C:up=\E[A:ce=\E[K:cd=\E[J:\ :so=\E[7m:se=\E[m:us=\E[4m:ue=\E[m:md=\E[1m:mr=\E[7m:me=\E[m:\ :ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:k1=\EOP:k2=\EOQ:k3=\EOR:\ :k4=\EOS:ta=^I:pt:sf=\n:sr=\EM:al=\E[L:dl=\E[M:ic=\E[@:dc=\E[P:\ :MT:ks=\E[?1h\E=:ke=\E[?1l\E>:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:\ :rs=\E[r\E<\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l:am:xn:AL=\E[%dL:DL=\E[%dM:\ :IC=\E[%d@:DC=\E[%dP:ti=\E7\E[?47h:te=\E[2J\E[?47l\E8:hs:\ :ts=\E[?E\E[?%i%dT:fs=\E[?F:es:ds=\E[?E: VS|vix19|vt100-x19|Visual X-19:\ :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:tc=xterm: #----------------- when these commands are performed (c-shell): set term=vix19 emacs the arrow keys (ku, kd, kr, kl) do not work. Checking the bindings with: M-x describe-bindings shows that the arrow keys HAVE NOT BEEN MAPPED. However, when these commands are performed (c-shell): set term=vt100-x19 emacs the arrow keys work fine. They are bound correctly. M-x emacs-version reveals: GNU Emacs 18.52.4 of Tue Aug 1 1989 on rags (berkeley-unix). My only guess is that emacs is making some internal assumptions based on seeing the characters 'vt100' as the term type. Naughty emacs. Guy T. Schafer Burlington Coat Factory Warehouse Data Processing Center HC 61, Box 1B Lebanon, NH 03766 ...!dartvax!coat!guy
agb@cscosl.ncsu.edu (Alan Bishop) (12/18/89)
In article <8912142026.AA14119@rags.coat.com> guy@coat.com (Guy T. Schafer) writes: >A section of our /etc/termcap file looks like this: [...] >VS|vix19|vt100-x19|Visual X-19:\ > :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:tc=xterm: [...] >the arrow keys (ku, kd, kr, kl) do not work. [...] >However, when these commands are performed (c-shell): > set term=vt100-x19 > emacs >the arrow keys work fine. [...] >My only guess is that emacs is making some internal assumptions based on >seeing the characters 'vt100' as the term type. Naughty emacs. You are correct that emacs does special processing for certain kinds of terminals. However, it is not done in a 'naughty' way. Please look under 'Terminal Init' in Info. (found under node 'Init File'). A quick solution is to make a link from <terminal-type>.elc to vt100.elc in either your lisp/term directory or in a personal lisp/term directory pointed to with EMACSLOADPATH (which should point to the lisp directory, not lisp/term). Note that the terminal-type should be the value of TERM with everything past the first "-" discarded. alan