Xref: utzoo comp.sys.att:11523 unix-pc.general:7295
Path: utzoo!utgpu!watserv1!watmath!uunet!glyph!ahh
From: ahh@glyph.UUCP (Andy Heffernan)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: Double-ESC
Message-ID: <1551@glyph.UUCP>
Date: 16 Jan 91 02:18:51 GMT
References: <37154@cup.portal.com> <1547@glyph.UUCP> <1549@glyph.UUCP> <1991Jan07.045230.2540@quest.UUCP>
Reply-To: ahh@glyph.UUCP (Andy Heffernan)
Followup-To: comp.sys.att
Organization: Moji Computing
Lines: 23

In article <1991Jan07.045230.2540@quest.UUCP> ssb@quest.UUCP (Scott Sheldon Bertilson) writes:
>
>  Just fiddled a little and found that the WIOCSESC can be used
>to turn it off or on.  Any non-zero argument enables it, and a
>0 argument disables it:
>	ioctl(0, WIOCSESC, 0);	/* disable */
>	ioctl(0, WIOCSESC, 1);	/* enable */

Yes, a fresh lead from my mysterious informant (actually it was
Bob Manson, manson@cis.ohio-state.edu -- thanks, Bob) redirected me 
to that ioctl, and it seems to work.  The return from the ioctl() also
appears to be the old state of the flag.  Very interesting.

Of course, I don't understand the point of the flag, why it gets
set in the first place, and why my news software continually fills in 
a stripped-down Followup-To line whenever I cross-post to unix-pc.general 
and comp.sys.att.

I suppose I ought to be satisfied (heh).

-- 
-------------------------------------------------------------------------
  Andy Heffernan	    文字		uunet!glyph!ahh