Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site aum.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!lll-crg!well!ptsfa!aum!freed From: freed@aum.UUCP (Erik Freed) Newsgroups: net.unix-wizards Subject: Re: Problem with curses ``getstr()''. Message-ID: <391@aum.UUCP> Date: Fri, 25-Oct-85 12:27:26 EDT Article-I.D.: aum.391 Posted: Fri Oct 25 12:27:26 1985 Date-Received: Sat, 26-Oct-85 19:40:00 EDT References: <137@oberon.UUCP> <311@ncr-sd.UUCP> Distribution: net Organization: The Aurora Systems Bunch Lines: 19 > In article <137@oberon.UUCP> mcooper@oberon.UUCP (Michael Cooper) writes: > >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. I can suggest one possible problem; If you don't set to crmode specifically I think that getstr() sets the terminal to RAW mode. Try calling cbreak or crmode. -- ------------------------------------------------------------------------------- Erik James Freed Aurora Systems San Francisco, CA {dual,ptsfa}!aum!freed