Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!brahms.udel.edu!weave From: weave@chopin.udel.edu (Ken Weaverling) Newsgroups: comp.editors Subject: Re: Editor for Primos Keywords: editor primos prime vi emacs Message-ID: <16842@chopin.udel.edu> Date: 3 Apr 91 05:54:04 GMT References: <1991Apr1.182117.9642@cs.ubc.ca> Organization: University of Delaware Lines: 23 In article <1991Apr1.182117.9642@cs.ubc.ca> manis@cs.ubc.ca (Vincent Manis) writes: >My experience with Primos is (fortunately!) about 4 years in the past, >but Prime does market a product called Emacs. Yes, as a sys admin of a Prime site, Emacs is available for Primos, but it isn't cheap. However, it integrates well with their compilers. You can compile from the editor and step through errors in all their languages. And if you have to code in RPG, it puts up the RPG forms for you. >... the only peculiarities I can remember are (1) it asked you what terminal >type you were on each time you ran it; (2) some frequently used Emacs >characters (I can't remember which ones, but ^S comes to mind) got >trapped by the system. Both of these are easily gotten around. For (1), set a global variable named .TERMINAL_TYPE$ to the terminal you use and emacs will get it from that. Their other full-screen apps query this same global var as well like TALK and ECL (The command line editor). The flow control (^s problem) can be disabled via TERM or SET_ASYNC commands -- >>>---> Ken Weaverling >>>----> weave@brahms.udel.edu