From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: "Douglas A. Gwyn" <DAGwyn@null.net>
Message-ID: <3B4F0AC0.A13D016E@null.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <20010713124934.B1573199E4@mail.cse.psu.edu>
Subject: Re: [9fans] how people learn things (was architectures)
Date: Fri, 13 Jul 2001 15:44:05 +0000
Topicbox-Message-UUID: ccb3cd44-eac9-11e9-9e20-41e7f4b1d025

presotto@plan9.bell-labs.com wrote:
>         while(`{read}){
>                 troff ... |lp -dstdout > x.ps
>                 page x.ps
>         }
> That's usually good enough for me to see quickly the effect of my
> changes.  However, WYSIWYG would be nicer.  It might even be worth
> doing.  Its just that when most of us get used to troff, the drive
> for doing a formatter for the uninitiated goes down.

Me, too.  I think it would be useful to have a program (script?)
that invoked a text editor ("sam" in my case) and whenever the
source file was modified (sam "w" command), fire up troff|proof
or whatever (including troff macros, etc.) in a *separate* window
to show the current formatted result.  The idea is to not
interrupt the editing session to view the result.