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

[rog@vitanuova.com]

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

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


[-- Attachment #2: Type: message/rfc822, Size: 2368 bytes --]

To: 9fans@cse.psu.edu
Subject: Re: [9fans] how people learn things (was architectures)
Date: Fri, 13 Jul 2001 15:44:05 GMT
Message-ID: <3B4F0AC0.A13D016E@null.net>

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.