Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!caip!seismo!gatech!cuae2!ihnp4!inuxc!pur-ee!pucc-j!purdue!narten From: narten@purdue.UUCP (Thomas Narten) Newsgroups: net.periphs,net.micro,net.wanted Subject: Re: update on **real** 19200 CRT Message-ID: <671@mordred.purdue.UUCP> Date: Wed, 16-Jul-86 21:42:05 EDT Article-I.D.: mordred.671 Posted: Wed Jul 16 21:42:05 1986 Date-Received: Fri, 18-Jul-86 04:49:45 EDT Organization: Department of Computer Science, Purdue University Lines: 38 Xref: watmath net.periphs:1141 net.micro:15110 net.wanted:9200 In article <65@winfree.UUCP> bdale@winfree.UUCP (Bdale Garbee) writes: >Paul -- Stay away from the Wyse-50. I bought about a half dozen at my former >job, and loved them dearly (especially the keyboards!) until I started running >Emacs on them... then I found out the hitch. The Wyse-50 emulates the >Televideo and similar terminals, and eats a screen location every time it >changes attribute modes on the screen. So, for example, an emacs mode line >done in inverse video will get horribly trashed as time goes on... rewriting >the screen with sort of fix it, but you LOSE a location on the screen (it >shows up as a blank) every time you change from normal to inverse to whatever. >Paul -- Stay away from the Wyse-50. I bought about a half dozen at my former >job, and loved them dearly (especially the keyboards!) until I started running >Emacs on them... then I found out the hitch. The Wyse-50 emulates the >Televideo and similar terminals, and eats a screen location every time it >changes attribute modes on the screen. So, for example, an emacs mode line >done in inverse video will get horribly trashed as time goes on... rewriting >the screen with sort of fix it, but you LOSE a location on the screen (it >shows up as a blank) every time you change from normal to inverse to whatever. We have lots of Wyse50s and we run emacs on them without problems. For a long while though, we had trouble with a character position getting lost. This was easily duplicated by splitting the screen into 2 windows, then scrolling backwards in the lower window (the one below the status line). The first character of the lower window would appear on the previous line, which was the status line. Our problem was not with the terminals, but with the version of Unipress emacs we were using. We finally fixed it and the terminals work great. Are you really sure that the terminals are at fault? We have over 75 here, and next to bit mapped displays (attached to workstations), they are our terminal of choice. -- Thomas Narten narten@purdue.EDU {ucbvax, ihnp4, allegra}!purdue!narten