Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!uvm-gen!banzai!john
From: john@banzai.PCC.COM (John Canning)
Newsgroups: comp.sys.att
Subject: Re: the shform program
Summary: key map fileS
Message-ID: <1990Jan7.221033.12368@banzai.PCC.COM>
Date: 7 Jan 90 22:10:33 GMT
References: <2413@ttardis.UUCP> <12494@cbnewsd.ATT.COM>
Reply-To: john@banzai.PCC.COM (John Canning)
Organization: The People's Computer Company, Williston, VT
Lines: 28

>In article <2413@ttardis.UUCP> rlw@ttardis.UUCP (Ron Wilson) writes:
>Since not all terminals have a line feed key (ie: \n), I would
>like to be able to have the shform program (and the associated
>form() and menu() functions accept return (ie: \r) as an
>alternative to line feed, aka Enter (ie: \n).
>

The easiest way to make this happen is to edit the key map file.
The key map file is defined in /etc/termcap as KM=/some/path/name.

For example, the UnixPC's entry reads KM=/usr/lib/ua/kmap.s4

We have the exact problem that Ron describes with the 605 terminals.
The Enter key is out of the way, and defaults to sending a carriage
return, rather than a line feed.  To make things happy, we added
this line to the key map file:

	Enter		\r

If you want the return key on the Unix PC to work the same way as the
enter key does, you can add the same line to the file /usr/lib/ua/kmap.s4.

Enjoy.

John Canning					...uunet!uvm-gen!banzai!john
The People's Computer Company			...attmail!banzai!john
Williston, Vermont				john@banzai.pcc.com
802-864-0747