From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how people learn things (was architectures)
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-mhoodfhnkywgceqwjwbdccjrtm"
Message-Id: <20010713161239.A8E3D199E7@mail.cse.psu.edu>
Date: Fri, 13 Jul 2001 17:22:13 +0100
Topicbox-Message-UUID: ccbdfeae-eac9-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-mhoodfhnkywgceqwjwbdccjrtm
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

> 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.

i remember ages ago reading in a paper about somebody
(on the Blit?) doing that.

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.


--upas-mhoodfhnkywgceqwjwbdccjrtm
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <9fans-admin@cse.psu.edu>
Received: from punt-1.mail.demon.net by mailstore for rog@vitanuova.com
          id 995039550:10:07433:2; Fri, 13 Jul 2001 15:52:30 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net
           id aa1007296; 13 Jul 2001 15:52 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id F0B48199F3; Fri, 13 Jul 2001 11:52:09 -0400 (EDT)
Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 577FB199C0
	for <9fans@cse.psu.edu>; Fri, 13 Jul 2001 11:51:11 -0400 (EDT)
Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1)
	id 15L57J-0007TM-00
	for 9fans@cse.psu.edu; Fri, 13 Jul 2001 16:44:33 +0100
Received: from GATEWAY by bath.ac.uk with netnews
	for 9fans@cse.psu.edu (9fans@cse.psu.edu)
To: 9fans@cse.psu.edu
Message-ID: <3B4F0AC0.A13D016E@null.net>
Organization: U.S. Army Research Laboratory
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)
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.5
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Fri, 13 Jul 2001 15:44:05 GMT

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.
--upas-mhoodfhnkywgceqwjwbdccjrtm--