elliott@madison.steinmetz (02/16/88)
Of late I have been delving into the exciting world of programming
clients for the NeWS window system, and I am hoping that someone might
know of the whereabouts of some Emacs-lisp code to implement a major
mode for editing Postscript, which will help with indentation,
closure, and the like. Currently my version of GNUEmacs treats ".ps"
files as plain text.
. . . . . . ... . . . . . . . . . . ... . .
Jim Elliott / ...!seismo!uunet!steinmetz!crd!elliott
/
"Don't look, son, it's / Jim_Elliott%mts@itsgw.rpi.edu [school]
a secular humanist!" / (or) elliott@ge-crd.arpa [work]
. . . . . . ... . . . . . . . . . . ... . .greely@teak.cis.ohio-state.edu (J Greely) (02/18/88)
I have such a mode, unfortunately it is written for Gosling Emacs, *not* GNU, and I do not have time or resources to convert it. I'm also not sure of the copyright status, but if it is permissible, I will email it to anyone who requests it. -=- -j, greely@satcom3.cis.ohio-state.edu "Tandoori to go. That's all they went out for, these people... Tandoori to go... and *instead*, they... they got..." -- Watchmen -----
bob@allosaur.cis.ohio-state.edu (Bob Sutterfield) (02/18/88)
For software that will provide not only postscript-mode but also a first cut at a native NeWS interface for GNU Emacs, you want to talk with Chris Maio at Columbia University, "chris@columbia.edu". I have worked a bit with his NeWS support stuff for GNU Emacs 18.49, and am quite impressed with the progress so far. I promised him just before Christmas and Urbana that I'd get some Pyramid bugs ironed out for him, and never got back to it again... The end of the README says: >Don't send mail to rms or bug-gnu-emacs@prep.ai.mit.edu; rms doesn't >want to have anything to do with this because of NeWS' proprietary >status. RMS, if this is in fact your policy I urge you to reconsider. Although it is understood to be unsupported by FSF, FSF already distributes code to support native GNU Emacs interfaces to at least one proprietary window system (SunView) and several proprietary operating systems (most extremely VMS). Why not agree to distribute code that supports another window system, on the same basis (he-wrote-it-don't-blame-FSF)? Why turn down people who offer to contribute code to FSF's efforts? -=- Bob Sutterfield, Department of Computer and Information Science The Ohio State University; 2036 Neil Ave. Columbus OH USA 43210-1277 bob@cis.ohio-state.edu or ...!cbosgd!osu-cis!bob