Path: utzoo!utgpu!attcan!uunet!peregrine!elroy!ames!nrl-cmf!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.sys.apple
Subject: Re: Kermit 3.83
Message-ID: <8276@brl-smoke.ARPA>
Date: 30 Jul 88 19:55:36 GMT
References: <22149853@WSUVM1> <8807251723.aa25106@SMOKE.BRL.ARPA>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 23

In article <8807251723.aa25106@SMOKE.BRL.ARPA> SEWALL@UCONNVM.BITNET (Murph Sewall) writes:
>... I'm told the VAX editors still won't work even with Xon/Xoff...

VAX is a hardware architecture; there is no "VAX editor".

There is a vendor-proprietary operating system called VAX/VMS;
since the vendor's terminals have required flow control since
almost the beginning of time, it is unlikely that any of the
system software provided in VAX/VMS doesn't support flow
control.  In fact, it is really the operating system's
terminal handler layer, not user-level programs such as editors,
that actually supports DC3/DC1 flow control.

A large fraction (perhaps as many as one-half) of VAXes run
some variant of the UNIX operating system.  The only editor in
common use on UNIX systems that disables the terminal handler's
support for flow control is EMACS (some variant thereof; there
are several).  This is clearly a design error, but the "owner"
of EMACS maintains that terminals should not need flow control
so he refuses to consider supporting it.  Reasonable variants
of EMACS (such as JOVE) have this fixed.  (The symptom of a
broken EMACS is that it automatically enters "search" mode
without being asked to.)