Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!lll-winken!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.sources.bugs
Subject: Re: atty on Sun 3
Message-ID: <1796@auspex.auspex.com>
Date: 9 Jun 89 18:36:58 GMT
References: <280@kurz-ai.UUCP> <68400002@sts> <1747@auspex.auspex.com> <16522@elroy.Jpl.Nasa.Gov>
Reply-To: guy@auspex.auspex.com (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 32

>I applied Guy's patch and everything seems to work fine except when I
>enter vi. Upon entering I'm immediately placed in insert mode. Also,
>upon leaving vi it appears that the keys are no longer bound. Anybody
>have any ideas?

The author made an inappropriate assumption about TIOCPKT_IOCTL;
apparently, he thought that you get them "for free" if you turn on
TIOCPKT or TIOCREMOTE mode.

Bad assumption - you *don't* get them for free.  You get them by turning
on an undocumented mode which I think I already spoke of as a hack
(which is probably in part why it's undocumented) *and* which is, as I
remember, mutually exclusive with TIOCPKT mode (I don't remember if the
information you can get with TIOCPKT mode, such as the
TIOCPKT_FLUSH{READ,WRITE} messages, can be gotten in that mode or not).

Try removing all code surrounded by

	#ifdef TIOCPKT_IOCTL
		...
	#endif

and removing the surrounding #ifdef/#endif on all code surrounded by

	#ifndef TIOCPKT_IOCTL
		...
	#endif

(or #undeffing TIOCPKT_IOCTL after all the include files have been
pulled in); I tried that (the #undeffing, actually) and it seemed to
work with "vi".  You shouldn't be any worse off than you are on any
vanilla 4.3BSD system....