From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: Re[2]: [9fans] how people learn things (was architectures)
Date: Thu, 2 Aug 2001 12:18:39 +0100 [thread overview]
Message-ID: <393106249@snellwilcox.com> (raw)
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.
----------------------------------------------------------------------
next reply other threads:[~2001-08-02 11:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 11:18 steve.simon [this message]
2001-08-03 9:04 ` Ralph Corderoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=393106249@snellwilcox.com \
--to=steve.simon@snellwilcox.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).