wescott@LNIC1.HPRC.UH.EDU (Andrew M. Wescott) (04/11/89)
I guess this is a timely message with all the questions about Emacs
under SR 10 that are floating around. Let me first say that I have
successfully compiled and linked Gnu Emacs 18.52 (with Apollo GPR
support included) on both a DN 10000 (SR 10.0.p) and a DN 3500
(SR 10.1). Let me also say that it was a lot of work. The
instructions (if you can call them that!) distributed with this
release assume you are a genius. It has been several months
since I accomplished this feat, so I don't remember all the
details off the top of my head. I would suggest that individual
users post their installation problems, and I will try to help.
However, my real motivation for this letter is to ask those of
you using Gnu 18.52 (there must be someone out there) a question.
We sought out Emacs not for direct use on the workstations
(even though it functions very nicely there), but instead we
sought it due to the demands of our remote users who come in
either over the network or through modem hook-ups. So now I
have Emacs running, but my remote users are still upset because
their VT100 and VT220 terminals due not work properly with it.
The main problem is that the C-S sequence used for the
incremental search locks the screen. When I remap the incremental
search, it only works as a "one time search" (it doesn't
remember the string). The real problem here is that I have not
loaded the VT100 or VT200 lisp libraries in /gnuemacs/lisp/term .
Well, I sought out advice from the author of the package (Leonard
Zubkoff - lnz@lucid.com) on how to do this. He told me to simply
set my TERM environment variable to VT100 before starting Emacs,
and everything should take care of itself. That's not quite true
as you must also add the line
(load (concat term-file-prefix (getenv "TERM")))
to you ~/.emacs file. Then a typical startup sequence (neglecting
the obvious aliases is something like:
% setenv TERM vt100 ; stty dec
% emacs
and the program responds with:
Loading term/vt100 ... done
and now you are in Emacs.
Of course everything works great except the C-S sequence which
still locks the screen. I've tried changing the stop escape
sequences in the shell to something other than ^S/^Q , but this
did not help my Emacs problem.
Will someone more familiar with using Emacs please straighten me
out before my users get violent with vi ?!
Sincerely,
Andrew Wescott
University of Houston
Department of Chemical Engineering
P.S. Rather than buying the distribution tape from ADDUS with
GnuEmacs 18.52 for the Apollo on it, you can download the
file /u2/emacs/apollo-emacs.tar.Z with ftp from the
following addresses: 128.52.14.14 , 128.52.22.14 , or
128.52.32.14 . Be sure to set you file type to binary,
and you can logon as yourself or as anonymous. I always
logon as myself and then use the password ftp.
krowitz@RICHTER.MIT.EDU (David Krowitz) (04/12/89)
Your problem with control-S is probably coming from your
SIO line configuration. Use /com/tctl to check if the
"insync" and/or "sync" parameters are set. If they are,
then the SIO line is using x-on/x-off handshaking (ie.
the control-S and control-Q characters) to control the
flow of data into ("insync") the Apollo and out to ("sync")
the terminal. Use "tctl" to turn off these parameters, and
use cts and/or rts to control the handshaking on the SIO
line. Of course, your cables from the terminals/modems to
the Apollo will have to include the extra wires used for
hardware handshaking, and the VT100 terminals will also
have to be configured to use hardware handshaking rather
than x-on/x-off. I have seen this problem with VT100's
connected to a variety of different systems. The problem
will occur on any system using x-on/x-off handshaking.
-- David Krowitz
krowitz@richter.mit.edu (18.83.0.109)
krowitz%richter@eddie.mit.edu
krowitz%richter@athena.mit.edu
krowitz%richter.mit.edu@mitvma.bitnet
(in order of decreasing preference)wescott@LNIC1.HPRC.UH.EDU (Andrew M. Wescott) (04/12/89)
I appreciate you advice, and I think it is correct. However, my DN 10000 has only BSD 4.3 installed, and tctl is not included in my /com. Any ideas on how to control xon-xoff within BSD ? Andrew Wescott University of Houston Department of Chemical Engineering
ced@apollo.COM (Carl Davidson) (04/12/89)
From article <8904112135.AA00230@lnic1.hprc.uh.edu>, by wescott@LNIC1.HPRC.UH.EDU (Andrew M. Wescott): > > Any ideas on how to control xon-xoff within BSD ? > You can use "stty" to re-define the start and stop characters. From the man page: > start c Set start character to c (default CTRL/Q). > stop c Set stop character to c (default CTRL/S). Hope this helps. Regards, -- Carl Davidson "Real life is too important to be taken seriously" Apollo Computer Inc. Chelmsford, MA 01824 ced@apollo.com