Xref: utzoo comp.lang.forth:569 comp.lang.postscript:973 comp.windows.news:790 comp.windows.misc:700 Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!haven!ncifcrf!toms From: toms@ncifcrf.gov (Tom Schneider) Newsgroups: comp.lang.forth,comp.lang.postscript,comp.windows.news,comp.windows.misc Subject: Re: Learning PostScript Keywords: Forth, Lisp, Interactive PostScript, NeWS Message-ID: <624@fcs280s.ncifcrf.gov> Date: 22 Sep 88 03:31:43 GMT References: <13613@mimsy.UUCP> <3492@phri.UUCP> <23378@wlbr.EATON.COM> <3496@phri.UUCP> <13655@mimsy.UUCP> <4227@adobe.COM> Reply-To: toms@ncifcrf.gov (Tom Schneider) Organization: NCI Supercomputer Center, Frederick, MD Lines: 22 In article <4227@adobe.COM> greid@adobe.UUCP (Glenn Reid) writes: >However, once you get past a pretty simplistic level, you get >very tired of retyping a line of code because you got it wrong: >... >This is about where you put the whole thing into a file, and do this >instead: >... >Which gets you back into batch mode, sort of.... Nope! I had two windows open. In one I had my editor, and I modified the code there. In the other window I ran psh. Then I could play by stuffing things from one window to the other (there might be an easier way to do this with a smarter editor like gemacs). So I could try out all kinds of things VERY quickly, which is the whole point of this discussion; to learn something it is best to be able to play around with it. So waiting around for the printer to print is no good... (I've assumed, for the purposes of this discussion, that a person has a choice between talking to the NeWS server via psh or to a printer. With no choice, either would be great.) Try this two window trick! Once you are set up, its great for testing all those neat \bells&whistles. And you end up with permanant code in a file if you want... Tom Schneider toms@ncifcrf.gov