Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!wuarchive!sdd.hp.com!uakari.primate.wisc.edu!xanth!abcfd20.larc.nasa.gov!ames!vsi1!zorch!xanthian From: xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) Newsgroups: comp.sys.amiga.tech Subject: Re: REXX command standards Message-ID: <1990Nov18.130116.14643@zorch.SF-Bay.ORG> Date: 18 Nov 90 13:01:16 GMT References: <1990Nov12.224249.18759@sisd.kodak.com> <533@epicb.com> <15874@cbmvax.commodore.com> Organization: SF-Bay Public-Access Unix Lines: 15 Dumb question I suppose, but could the problem of having M edit command providers talk to N editors be ameliorated by writing an intermediate AREXX module that accepted a common stripped down consensual editing command set and emitted commands translated for editor n of N? I.e, this one maintained piece of software would have to be kept current with the superset of editor commands, but all the programs using it to control editors could remain oblivious to just which editor was out there, while the intermediary put up a requestor or grabbed an ENV: entry to learn which editor/port it should address. Just a thought. It worked with graphics standards, that's why there's a CGM. Kent, the man from xanth.