Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!decuac!bacchus.pa.dec.com!bacchus!mwm From: mwm@raven.relay.pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga.tech Subject: Re: REXX command standards Message-ID: Date: 16 Nov 90 21:27:59 GMT References: <3800@mindlink.UUCP> <1990Nov14.033931.12883@evax.arl.utexas.edu> Sender: news@wrl.dec.com (News) Organization: Missionaria Phonibalonica Lines: 29 In-Reply-To: hill@evax.arl.utexas.edu's message of 14 Nov 90 03:39:31 GMT In article <1990Nov14.033931.12883@evax.arl.utexas.edu> hill@evax.arl.utexas.edu (Adam Hill) writes: I would just like a set defined for CERTAIN things: Editors - Open, Close, Move To Line, Move To Word, Query Word (Left|Right) of Cursor, Cut, Paste, Copy, Search and Replace. Cut, Paste and Copy _what_? Before you dive into designing a standard, you need to design a couple of other things. I think, first and foremost, you need a standard as to what are "acceptable" formats for the Rexx commands specified by a standard. It has to be something that will fit into the existing commands for most editors. For example, choosing some subset of the mg3 command set just _won't_ cut it. Mg3 is a good example of how Rexx commands shouldn't look - because the Rexx command set is largely the GNU Emacs command set, which was designed for a different purpose. Other editors are also good examples of what not to do. The other thing you have to do before starting on a standard is design the command set. Just throwing stuff in as needed is a good way to create problems. The above set looks like it's in that category.