Path: utzoo!utgpu!water!watmath!uunet!cbmvax!ditto From: ditto@cbmvax.UUCP (Michael "Ford" Ditto) Newsgroups: unix-pc.bugs Subject: Re: Bug report--window driver 3.51 Summary: { set -o emacs; } or { set -o vi viraw; } will help a bit Keywords: window typeahead lossage Message-ID: <4785@cbmvax.UUCP> Date: 21 Sep 88 06:20:43 GMT References: <10552@stb.UUCP> <761@rush.cts.com> <10581@stb.UUCP> <404@amanue.UUCP> Reply-To: ditto@cbmvax.UUCP (Michael "Ford" Ditto) Organization: Commodore Technology, West Chester, PA Lines: 29 In article <404@amanue.UUCP> jr@amanue.UUCP (Jim Rosenberg) writes: >But what is interesting is that if in ksh I remember to type ESC before the >window switch, woila, when I come back *NO* characters have been eaten. Hittng >ESC causes ksh to consume all of the charaters typed before going into [ ... ] >[BTW: I use the vi mode of ksh; no flames please if the character to enter >edit mode for emacs mode isn't ESC -- you get the idea.] [ I hope this isn't considered a flame: ] In emacs mode, ksh is always in raw mode so this doesn't happen. In vi mode, you can set the "viraw" option to make ksh always use raw mode, and then you won't have the problem (at a slight system performance cost -- not even worth worrying about on the Unix PC, if anywhere). As Jim pointed out, the above methods only help when sitting at the ksh prompt; when running programs in cooked mode the "bug" will still happen. If anyone's taking votes, I call it a bug and would fix it if it were up to me. -- -=] Ford [=- . . (In Real Life: Mike Ditto) . : , ford@kenobi.cts.com This space under construction, ...!ucsd!elgar!ford pardon our dust. ditto@cbmvax.commodore.com