home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.editors
- Path: sparky!uunet!sun-barr!cs.utexas.edu!torn!cunews!nrcnet0!bnrgate!bmerh85!bmers248!sjane
- From: sjane@bmers248.bnr.ca (sjs)
- Subject: elvis 1.6, Sun Sparc and cursors keys
- Message-ID: <1992Aug18.201352.2155@bmerh85.bnr.ca>
- Keywords: elvis 1.6 cursor key troubles on Sun Sparc
- Sender: news@bmerh85.bnr.ca (Usenet News)
- Organization: Irrelevant, Ottawa, Canada
- Date: Tue, 18 Aug 92 20:13:52 GMT
- Lines: 21
-
- My sysadmin just upgraded to elvis 1.6 from elvis 1.5. One of the
- changes in 1.6 is:
- The :ks=:ke=: termcap strings aren't used anymore. Those strings are
- supposed to be used to put the keypad in "application mode", but it seems
- that editors aren't applications in the eyes of termcap entry writers.
- The :ks=: string was making the arrow keys send goofy codes instead of the
- normal codes defined in :ku=: etc.
-
- What this meant to me, running elvis on a Sun Sparc II, OW2, X11R4, from an
- xterm, is that my cursor keys stopped working. Completely. They just
- beeped at me.
-
- If you run into this problem, you can either get your sysadmin to change back
- to elvis 1.5 or you can alter your .termcap file (ask a guru) to change your
- :ku, :kd, :kr, :kl to be \E[A, \E[B, \E[C, \E[D. I'm not absolutely positive
- if the latter solution will solve all your problems, because my sysadmin added
- :ks & :ke back into elvis 1.6 for me.
-
- -sjs
- --
- It's not irrelevant; it's a hippopotamus. sjane@BNR.CA
-