Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!columbia!caip!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!ecn-pc!sandersr From: sandersr@ecn-pc.UUCP (Robert C Sanders) Newsgroups: net.periphs,net.micro,net.wanted Subject: Re: update on **real** 19200 CRT Message-ID: <639@ecn-pc.UUCP> Date: Tue, 12-Aug-86 14:02:25 EDT Article-I.D.: ecn-pc.639 Posted: Tue Aug 12 14:02:25 1986 Date-Received: Wed, 13-Aug-86 06:28:10 EDT References: <671@mordred.purdue.UUCP> <71@winfree.UUCP> <839@usl.UUCP> <475@mcgill-vision.UUCP> Reply-To: sandersr@ecn-pc.UUCP (Robert C Sanders) Organization: Electrical Engineering Department , Purdue University Lines: 79 Xref: mnetor net.periphs:505 net.micro:5827 net.wanted:3664 In article <475@mcgill-vision.UUCP> mouse@mcgill-vision.UUCP writes: >In article <839@usl.UUCP>, elg@usl.UUCP (Eric Lee Green) writes: >> In article <71@winfree.UUCP> bdale@winfree.UUCP (Bdale Garbee) writes: >>> The problem we ran into was specifically with inverse video and >>> underlining, in that we seemed to always get a "space" added in >>> before and after each line segment that was in a different mode. We >>> were running Gosling's Emacs, and had access to sources. I don't >>> think it was the software's fault, >> We have a terminal room of TVI910 terminals, which are functionally >> similiar to the Wyse 50. When using Gosling Emacs, we would have the >> same problem as mentioned above ("spaces" in mode lines). We solved >> the problem simply: by deleting Gosling Emacs off of disk, and >> replacing it with GNU Emacs 17.56. Problem solved. Q.E.D. >> Definitely a software problem and not a problem with the terminal. >I am *fed* *up* with all these postings claiming that this problem is >due to this or that, for they all miss something! It is really three >things put together: >1- TVI was silly enough to build a magic-cookie terminal, >2- There's no magic-cookie support in Gosmacs, and >3- Someone hacked out a TVI termcap entry carelessly. >The simplest way to fix it is to clean up the tvi termcap entry. Get >rid of the silly \EG so and se strings and use \E( and \E) (bright and >dim). Provided you never use protect mode, which is inappropriate for >Emacs anyway, this works fine (it's what we're using). This is wrong way to adjust the termcap entry, and screws-up the termcap even further. You should read the manual (termcap(5)), and look at the following: TERMCAP(5) UNIX Programmer's Manual TERMCAP(5) NAME termcap - terminal capability data base SYNOPSIS /etc/termcap [ a lot deleted ...] CAPABILITIES (P) indicates padding may be specified (P*) indicates that padding may be based on no. lines affected Name Type Pad? Description [ a lot deleted ...] ms bool Safe to move while in standout and underline mode se str End stand out mode sg num Number of blank chars left by so or se so str Begin stand out mode uc str Underscore one char and move past it ue str End underscore mode ug num Number of blank chars left by us or ue ul bool Terminal underlines even though it doesn't overstrike us str Start underscore mode xs bool Standout not erased by writing over it (HP 264?) Usually, for terminals that do not have underline, but have "bright" capability, the 'us' sequence sends the underline code; the "bright", "dim", "normal" given in the previous posting. GNUemacs programs around some the faults in the termlib by looking at the termcap for 'sg' and 'ug', and corrects for it. We here at Purdue's ECN have many, many Lear Siegler ADM5 terminals, which are brain-damaged the same way at the TVI (or my TEC at home) -- they all leave a space for the "\EG" standout/standend sequence. You have to look for this, and display the inversed string one position earlier, and start the next one also one space earlier. Therefore, IT IS A FUNCTION OF THE SOFTWARE TO LOOK FOR THIS TERMCAP ENTRY AND CORRECT FOR IT!! Also, look at the termcap for your TVI: does it have the 'sg#1' entry? Ours does, and VI and EMACS run fine. - bob -- Continuing Engineering Education Telecommunications Purdue University ...!ihnp4!pur-ee!pc-ecn!sandersr Let's make like a BSD process, and go FORK-OFF !! -- bob (and "make" a few children while we're at it ...)