Path: utzoo!utgpu!water!watmath!clyde!att!pacbell!ames!haven!umd5!adm!cmcl2!phri!bc-cis!john
From: john@bc-cis.UUCP (John L. Wynstra)
Newsgroups: comp.unix.questions
Subject: Echoing control characters on the crt (System V)
Keywords: ctlecho
Message-ID: <1278@bc-cis.UUCP>
Date: 20 Aug 88 18:07:57 GMT
Reply-To: john@bc-cis.UUCP (John L. Wynstra)
Distribution: na
Organization: Brooklyn College of CUNY, Brooklyn, NY
Lines: 26


	I had an experience the other day.  I was "doctoring" a program I
had running on one machine [the Altos 2086, runs XENIX 3.4] to run on the
Altos 1000 [in effect a System V on a 386].  The program emits a Ctrl-G
in response to an error (via "curses" in raw mode, no echo).  On the 2086
a bell sounds.  On the Altos 1000 it displays ^G on the screen.

	I immediately thought of Berkeley's ctlecho feature on the stty,
and checked our manual, but discovered no such analog on the System V.

	Just to further define this problem, I tried an experiment, I did
a stty -echo and keyed in a Ctrl-G, the Altos 2086 replies "<bell sound>: not
found", but on the Altos 1000 it replies "^G: not found".  What is going on
here?  Is there a way I can tell the System V tty driver to not echo control
characters, a la Bsd's "stty -ctlecho"?

--
	John L. Wynstra
	"the 40-year-old rookie"
	US mail:	Apt. 9G, 43-10 Kissena Blvd., Flushing, N.Y., 11355
					 ________________________________
	UUCP:	rutgers --> cmcl2 --,	| domain style: john@bc-cis.UUCP |
		ihnp4 --> allegra --|	`--------------------------------'
				    +--> phri --> bc-cis --> john
			princeton --|
			columbia  --'