Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!psuvax1!gondor.psu.edu!schwartz
From: schwartz@gondor.psu.edu (Scott E. Schwartz)
Newsgroups: comp.emacs
Subject: Re: memacs3.9
Message-ID: <3141@psuvax1.psu.edu>
Date: Mon, 30-Nov-87 12:16:38 EST
Article-I.D.: psuvax1.3141
Posted: Mon Nov 30 12:16:38 1987
Date-Received: Thu, 3-Dec-87 04:14:02 EST
References: <791@uop.EDU>
Sender: netnews@psuvax1.psu.edu
Reply-To: schwartz@gondor.psu.edu (Scott E. Schwartz)
Organization: Penn State University, University Park, PA
Lines: 19
Keywords: uEmacs
Summary: why do it right?

In article <791@uop.EDU> exodus@uop.EDU (G. Onufer) writes:
>
>I compiled me3.9 on our Sun systems here.  We use Televideo 905's for the
>most part and there seems to be a small problem with them.  me3.9 starts
>repainting the screen at column 1 (as opposed to column 0) and when you
>start entering text, it is double spaced (ie: type "aaa" get "a a a").

I have not seed 3.9 yet, but on all previous versions of microemacs
(and lots of other programs, for that matter) the author uses the termcap
entries "so" and "se" to highlight characters, but chooses to ignore
"sg" which tells how much space the magic cookies take up.  Uemacs is printing
so and se and not realizing that they screw up the output on your terminal.
Solutions: you can patch uemacs to never use so/se (easy), you can fix uemacs
to do it right (someone posted patches for 3.7 last year),
or you can alter your termcap entry to not define them.  In any event,
someone should let the author know this is going wrong.


-- Scott Schwartz            schwartz@gondor.psu.edu