Path: utzoo!mnetor!uunet!husc6!spdcc!dyer From: dyer@spdcc.COM (Steve Dyer) Newsgroups: comp.unix.microport Subject: Re: odd behavior in read Message-ID: <726@spdcc.COM> Date: 14 Mar 88 13:19:52 GMT References: Organization: S.P. Dyer Computer Consulting, Cambridge MA Lines: 14 The behavior of read() you describe, while very unBerkeleylike, is not a bug in your particular version of UNIX 386; it's the behavior you'd get in any version of UNIX other than 4.[23], including V6 and V7. Trouble is, now in S5 you can specify to the TTY driver the minimum number of chars to wait for and/or a time to wait. This is different from RAW and CBREAK modes in V7-derived UNIX systems, whose semantics always guarantee that a single character (or -1) is returned, and doesn't mesh well with the older handling of signals. Why don't you try setting the minimum number of chars to wait to 1, to get the same behavior as a V7 system? This should make Jove work as well as any screen editor did under V7. -- Steve Dyer dyer@harvard.harvard.edu dyer@spdcc.COM aka {ihnp4,harvard,husc6,linus,ima,bbn,m2c}!spdcc!dyer