Xref: utzoo comp.lang.forth:570 comp.lang.postscript:974 comp.windows.news:791 comp.windows.misc:701
Path: utzoo!attcan!uunet!steinmetz!barnett@grymoire.steinmetz.ge.com
From: barnett@grymoire.steinmetz.ge.com (Bruce G. Barnett)
Newsgroups: comp.lang.forth,comp.lang.postscript,comp.windows.news,comp.windows.misc
Subject: Re: type checking (I want PostScript) -- give NeWS a try!
Keywords: Forth, Lisp, Interactive PostScript, NeWS
Message-ID: <12197@steinmetz.ge.com>
Date: 21 Sep 88 13:15:52 GMT
References: <13613@mimsy.UUCP> <3492@phri.UUCP> <23378@wlbr.EATON.COM>
Sender: news@steinmetz.ge.com
Reply-To: barnett@steinmetz.ge.com (Bruce G. Barnett)
Followup-To: comp.windows.news
Organization: GE Corp. R & D, Schenectady, NY
Lines: 21
In-reply-to: mh@wlbr.EATON.COM (Mike Hoegeman)
In article <23378@wlbr.EATON.COM>, mh@wlbr (Mike Hoegeman) writes:
> You can just fire up a psh (PostScript Shell)
A much easier way is to use the postscript.el mode that
comes with the GNU-emacs/NeWS package on columbia.edu.
Then edit your postscript file, type C-c C-c, and the postscript
is displayed on the screen. Change one line, whatever, type C-c C-c again,
and you see the differences.
You may have to write something that draws a blank box as the image is
temporary, and a new image overwrites the old one. (without clearing).
But this is a very easy way to learn what postscript is doing, and
requires NO knowledge of NeWS other than starting, installation, etc.
You can learn NeWS by adding extensions later.
--
--
Bruce G. Barnett
uunet!steinmetz!barnett