richard@kuhub.cc.ukans.edu (RICHARD KERSHENBAUM) (02/17/89)
We're presently attempting to install CCA Emacs Version 166 on a VAX running VMS V4.7. Because of restrictions of our local X.25 network, we're currently forced to configure nearly all user terminals as 7-bit, even-parity. Emacs seems to expect terminals to be configured for 8-bits, no parity; it's treating the parity bit as data on incoming characters. Some of our users seem determined to use ASCII characters containing an odd number of "1" bits. We think they probably ought to be able to do that... :-) CCA Emacs V164 didn't have this peculiarity, but it's developing a bad case of software rot; we really need to upgrade to a newer release. Has anyone encountered this problem? Is there a workaround? -- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | Richard M. Kershenbaum Bitnet: richard@ukanvax | | The University of Kansas Internet: richard@kuhub.cc.ukans.edu | | Computer Center Phone: (913)-864-0445 | | Lawrence, Kansas 66045 | +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
gjc@bu-cs.BU.EDU (George J. Carrette) (02/18/89)
My humble observation: Gnu Emacs is better supported than CCA emacs. (better redisplay techniques, speed, DECWindows support, you name it). Therefore your best bet is to upgrade to Gnu Emacs, and spend your support money elsewhere.