forceten@dalcs.UUCP (Safeguard Business Systems) (10/29/88)
][b
I'm having trouble using GNU Emacs Version 18.41 under VMS 4.?.
I have a terminal which is a superset of a vt100, but VMS thinks it
is a vt100. I have the termcap file in my own directory, and it is
being read properly by emacs. My initialization file is also being
read properly by emacs.
But no matter what I do to the termcap file, the system/emacs always
acts as though it assumed I have only a vt100. If I do
$ SET TERMINAL/DEVICE_TYPE=FT1
and set up a termcap with ft1 and vt100 as aliases everything works.
This termcap is the only one for vt100 in the file. But if I do
$ SET TERMINAL/DEVICE_TYPE=VT100
the damn thing reverts to being a moronic vt100 again! Is VMS looking at
the output and translating it into stupid equivalent sequences? If so
how do I get rid of this behaviour? And No, I can't check for vt100 in
my LOGIN.COM file and switch to ft1, because sometimes I do use the real
thing.
||!][b
--
Neil S. Erskine MT&T - (902) 453-4915
Safeguard Business Systems USENET { garfield, watmath, utzoo!utai,
6080 Young St, Suite 901. seismo, uunet } !dalcs!force10!erskine
Halifax, N.S. B3L-4H9
robertr@ozvax.GWD.TEK.COM (Robert ) (11/03/88)
In article <3064@dalcs.UUCP> forceten@dalcs.UUCP (Safeguard Business Systems) writes: > > I'm having trouble using GNU Emacs Version 18.41 under VMS 4.?. > I have a terminal which is a superset of a vt100, but VMS thinks it > is a vt100. I have the termcap file in my own directory, and it is > being read properly by emacs. My initialization file is also being > read properly by emacs. > > But no matter what I do to the termcap file, the system/emacs always > acts as though it assumed I have only a vt100. If I do > > $ SET TERMINAL/DEVICE_TYPE=FT1 > > and set up a termcap with ft1 and vt100 as aliases everything works. > This termcap is the only one for vt100 in the file. But if I do > > $ SET TERMINAL/DEVICE_TYPE=VT100 > > the damn thing reverts to being a moronic vt100 again! Is VMS looking at > the output and translating it into stupid equivalent sequences? If so > how do I get rid of this behaviour? And No, I can't check for vt100 in > my LOGIN.COM file and switch to ft1, because sometimes I do use the real > thing. Neil, My first question is: Do you have the logical name EMACSVARS_TERM defined in one of your logical name tables?? If you don't then add a command line to define this logical name to your login.com. GNU looks for this logical first to determine your terminal type. However, if it (gnu) can't find a definition for this logical name, it will grab the DEVICE_TYPE field for the specific port that your connected to. If you already have definded this logical name in one of your tables, make sure that the case (thats upper/lower case) for any alpha characters in the termcap entry are the same as your EMACSVARS_TERM logical name definition. IE: I have a Tektronix 4207, the termcap entry is tek4207 (one of them anyway), so I have my login.com make the following logical name definition if I'm logging in interactively: $ define emacsvars_term "tek4207" NOTE: the inclosing double quotes are required to keep the logical name trans- lation in lower case. This allows me to keep the DEVICE_TYPE parameter for my communication port as a VT100. Tip ------------------------------------------------------------------------------- Robert L. (Tip) Rouse sysprog@madvax.gwd.tek.com (or) Systems Programmer robertr@ozvax.gwd.tek.com Tektronix, Inc. IDG/ITD P.O. Box 1000 M/S 63-523 (503) 685-4539 Wilsonville, Oregon 97070 -------------------------------------------------------------------------------