Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site oberon.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!petrus!bellcore!decvax!ittatc!dcdwest!sdcsvax!sdcrdcf!oberon!mcooper
From: mcooper@oberon.UUCP (Michael Cooper)
Newsgroups: net.unix-wizards
Subject: Problem with curses ``getstr()''.
Message-ID: <137@oberon.UUCP>
Date: Wed, 16-Oct-85 23:47:37 EDT
Article-I.D.: oberon.137
Posted: Wed Oct 16 23:47:37 1985
Date-Received: Fri, 25-Oct-85 01:44:46 EDT
Distribution: net
Organization: University Computing Services, U.S.C.
Lines: 25

Ahh, yes.  Another curses problem.  Or at least it is a problem 
that curses is having with me!  I am trying to get a string from a window
with wgetstr(win, buf).  Now I checked both in the documentation and
getstr.c and both say that getstr reads up to a newline ('\n') or EOF.
When I put this into practice, though, it just plain doesn't work.  It
keeps reading everything in.  This includes newlines, SIGINTR, SIGKILL,
SIGSUSP.  The only way to get out of it is to use another terminal and kill
the program's process.

Would somebody care to point out something that I missed?  Or is it 
just another bug from the braindamaged Berzerkeley?  If so, anybody want to
volunteer a fix?


-- 
					Michael Cooper

+----------------------------------------------------------------------------+
| University of Southern California - University Computing Services	     |
|============================================================================|
|	Usenet: ...!{uscvax, sdcrdcf, engvax, scgvaxd, smeagol,	             |
|		    cit-vax, brand, dworkin, tyger, omnilax}!oberon!mcooper  |
|	Bitnet: mcooper@uscvaxq, mcooper@jaxom 				     |
|	  ARPA:	mcooper@usc-oberon.arpa	  OR   mcooper@usc-eclc.arpa  	     |
+----------------------------------------------------------------------------+