From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: steve.simon@snellwilcox.com
Subject: Re[2]: [9fans] how people learn things (was architectures)
Message-Id: <393106249@snellwilcox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Id: <393106249-1@snellwilcox.com>
Content-Transfer-Encoding: 7bit
Date: Thu,  2 Aug 2001 12:18:39 +0100
Topicbox-Message-UUID: d884ef0e-eac9-11e9-9e20-41e7f4b1d025


Hi,

Wasn't this in Kernighan and Pike (The Unix Programming Enviroment) -
waitfile.c I don't have it to hand, but I'am pretty sure its there.

-Steve


____________________Reply Separator____________________
Subject:    Re: [9fans] how people learn things (was architectures)
Author: 9fans@cse.psu.edu
Date:       02/08/01 11:27

Hi,

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

This is effectively what I've done in the past on Unix.  Either
instruct your version of vi to execute a command on every write of the
file or have a script watching the file which does `groff ... >x.ps'.

gv, a GhostScript viewer, already has an option to refresh when the
PostScript file changes.  This has the advantage that you remain at the
bottom of page 5 rather than a new window opening on page 1.


Ralph.



----------------------------------------------------------------------
The contents of this communication are confidential to the normal user of
the email address to which it was sent.  If you have received this email
in error, any use, dissemination, forwarding, printing or copying of this
email is strictly prohibited.  If this is the case, please notify the sender
and delete this message.
----------------------------------------------------------------------