Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!linus!philabs!cmcl2!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>)
Newsgroups: net.info-terms
Subject: Re: Please make your programs ignore the "am" capability
Message-ID: <2106@brl-tgr.ARPA>
Date: Sun, 13-Oct-85 20:06:12 EDT
Article-I.D.: brl-tgr.2106
Posted: Sun Oct 13 20:06:12 1985
Date-Received: Tue, 15-Oct-85 05:07:29 EDT
References: <70@druhi.UUCP> <227@epicen.UUCP> <2857@sun.uucp> <186@l5.uucp> <218@ho95e.UUCP>
Organization: Ballistic Research Lab
Lines: 22

> Another thing to avoid is terminal descriptions or software that ASSUME they
> can turn off NL->LFCR translation, so they use control-J to mean
> "move straight down".  In a complex environment (e.g. cu, some window programs,
> some LAN software), the software on the machine running the editor turns this
> off, and the information doesn't get to the mahine controlling the terminal.

If the termcap/terminfo terminal description says that do/cud1 is "^J",
then that is what should be used; otherwise, it should NOT be assumed.

If you have a brain-damaged LAN or window manager, then you should
install a corresponding termcap/terminfo terminal description to be
used under those circumstances.

In all cases, software is entitled and required to use just those
capabilities described in the terminal description and must make
no other assumptions.

Implementation note:  I prefix comments describing terminal set-up
modes and other prerequisites to the termcap/terminfo descriptions
that I write.  This seems like the only way of eliminating any
confusion in these days of terminals that emulate numerous other
terminals and stupid LAN designs.