🚀 go-pugleaf

In article <1936@tektools.UUCP> kathyv@tektools.tek.com (Kathy Vineyard) writes:
>Index:	/usr/src/usr.lib/libcurses/cr_tty.c 4.3BSD
>
>Description:
>	When running a program that uses curses, the user environment
>	was sometimes getting stepped on.  This resulted in getting the
>	famed "x: is not an identifier" from /bin/sh when it was
>	exec'd.  This happened only when using a termcap which had
>	multiple names ( > 2 ) for the termcap entry, the third name of
>	the entry was the one being used by the user, and the length of
>	that third name was at least 2 less than the length of the
>	second name.
>
>Repeat-By:
>	Use a termcap which has it's names set up like:
>
>	   Mc|aaa-c|aaa|aaa with separate scrolling and editing areas:\
>

My environment was always getting stepped on. I was using the FIRST name
in the termcap entry. My termcap entry is:
# "00: is not an identifier" entry
h5|h1500|H5|H1500|haz1500|HAZ1500|hazeltine 1500:\

The fourth item pointed to in the array of pointers pointed to by environ
was getting set to the null terminated string "00". I isolated initscr()
as the culprit using dbx about 15 mins ago.

-- 
--==---==---==--
.. And hast thou slain the Jabberwock? ..

ARPA: cgs@umd5.UMD.EDU     BITNET: cgs%umd5@umd2
UUCP: ..!seismo!umd5.umd.edu!cgs