Re: [9fans] how people learn things (was architectures)

["david presotto" <presotto@plan9.bell-labs.com>]

With the loop I sent, I just hit newline in the window every time
I want to see a new copy of the layedout document.  It's not
automatic, just easy.  Of course with the speed of processors these
days, Doug's suggestion of just doing it when the file changes is
fine by me.  The other window is usually covered up anyways.

Rob was working on a much nicer WYSISYG editor that put out
a tagged file.  Perhaps he'll get back to it in the near future.
----- Original Message -----
From: Douglas A. Gwyn <DAGwyn@null.net>
To: <9fans@cse.psu.edu>
Sent: Monday, July 16, 2001 4:54 AM
Subject: Re: [9fans] how people learn things (was architectures)


> rog@vitanuova.com wrote:
> > i remember ages ago reading in a paper about somebody
> > (on the Blit?) doing that.
>
> Yeah, it was fairly common for us Blit-family users.
>
> > personally, i think it's quite nice *not* to have the visual
> > feedback all the time - that way i can concentrate
> > on the content of the text i'm creating without being
> > distracted by occasional display glitches.
>
> Note that i suggested it should occur only when one has
> just written out the editor buffer.  Usually I do this
> only at fairly well-defined stages of completion, which
> is a natural time to have the result presented for
> inspection.
>
> Also, you can ignore the refresh going on in another
> window.  Many people have stuff going on in other windows
> that the one they're currently focussed on.
>