Annotation of 43BSDReno/usr.bin/tn3270/distribution/ultrix.curses, revision 1.1.1.1

1.1       root        1: Return-Path: [email protected]
                      2: Received: from ucbvax.berkeley.edu
                      3:        by violet.berkeley.edu (5.54 (CFC 4.22.3)/1.16.17l)
                      4:        id AA23846; Wed, 30 Mar 88 19:54:24 PST
                      5: Received: by ucbvax.berkeley.edu (5.59/1.26)
                      6:        id AA09851; Tue, 29 Mar 88 23:25:19 PST
                      7: Received: by mtxinu.UUCP (5.51/4.7)
                      8:        id AA05135; Tue, 29 Mar 88 17:32:01 PST
                      9: Message-Id: <[email protected]>
                     10: Date: Thu, 17 Mar 88 11:06:10 pst
                     11: From: [email protected] (Greg Minshall)
                     12: To: mtxinu!minshall
                     13: 
                     14: Path: kinetics!zehntel!varian!ptsfa!pacbell!ames!ll-xn!husc6!panda!teddy!jpn
                     15: From: [email protected] (John P. Nelson)
                     16: Newsgroups: comp.bugs.4bsd
                     17: Subject: Re: Ultrix curses problem
                     18: Keywords: curses ultrix bug fix
                     19: Message-ID: <[email protected]>
                     20: Date: 14 Mar 88 19:43:39 GMT
                     21: References: <[email protected]>
                     22: Reply-To: [email protected] (John P. Nelson)
                     23: Organization: GenRad, Inc., Concord, Mass.
                     24: Lines: 21
                     25: 
                     26: >I have found the bug, fixable as above, in both Ultrix 1.2 and 2.0.  Feedback
                     27: >from those brave souls who have brought up 2.2 would be most welcome.
                     28: 
                     29: Yup, the bug exists in Ultrix 2.2 as well.  I have reported this bug to
                     30: DEC support every time we get a new release.  I assume that my bug reports
                     31: are getting filed (in the circular file).
                     32: 
                     33: It is clear that whoever made this "fix" at DEC had no understanding
                     34: of curses whatsoever.  As in the earlier posting, the bug can be fixed
                     35: by replacing the definitions of the nl() and nonl() macros in curses.h with:
                     36: 
                     37: #define nl()    (_tty.sg_flags |= CRMOD,_pfast = _rawmode,stty(_tty_ch, &_tty))
                     38: #define nonl()  (_tty.sg_flags &= ~CRMOD, _pfast = TRUE, stty(_tty_ch, &_tty))
                     39: 
                     40: - john nelson.
                     41: 
                     42: P.S.  I did reach someone at DEC who would listen (Thanks Chet!)  My
                     43:       understanding is that they have no plans to fix this bug, as curses
                     44:       is now "owned" by some group in England, who is working on a port of the
                     45:       terminfo curses for Ultrix 2.4.  I'm just pissed that my bug reports
                     46:       submitted for Ultrix 1.2 and 2.0 were ignored.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.