🚀 go-pugleaf

In article <328@dcsun21.dataco.UUCP> mcphail@dataco.UUCP (Alex McPhail) writes:
>I have MKS Toolkit, and DesqView (the latest version).  When I
>try to run 'vi' in MKS Toolkit while I am in a DesqView window,
>it starts to run, then it beeps forever.  

You must set the DESQview window to indicate that the application does
not write text directly to the screen and not to virtualise text and
graphics.  The beeping is caused by vi's clear screen sequence which
writes SPACE followed by \007 (character and attribute screen bytes).
It does this for each screen location.  If you watch the cursor, you
will notice that it moves before each beep.  This will take a long time
to complete since the BEL \007 will take a while to `print'.  DESQview
is somehow converting the screen writes to "printing".  This will be
fixed in the next release.
-- 
Andy Toy <andy@mks.com>                       UUCP: ...!uunet!watmath!mks!andy
Technical Support <support@mks.com>                     Phone: +1-519-884-2270
Mortice Kern Systems Inc. <inquiry@mks.com>             Phone: +1-519-884-2251
35 King Street North, Waterloo, Ontario N2J 2W9, CANADA   Fax: +1-519-884-8861