Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!manuel!ccadfa!prolix!dac
From: dac@prolix.pub.uu.oz.au (Andrew Clayton)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: "Hope To See" Features in the next JR-COMM
Message-ID: <18ac1c44.ARN2ae9@prolix.pub.uu.oz.au>
Date: 12 Feb 91 11:16:52 GMT
References: <1991Feb8.222749.19507@ims.alaska.edu> <paul.0401@theborg.mlb.fl.us>
 <970@faatcrl.UUCP>
Reply-To: dac@prolix.pub.uu.oz.au
Followup-To: comp.sys.amiga.datacomm
Organization: More like Mis~, really.
Lines: 21

In article <970@faatcrl.UUCP>, Jack Radigan writes:

> paul@theborg.mlb.fl.us (Paul Aidukas, Sys Admin.) writes:
> 
> >I REALLY need an ARexx port in JR-Comm!!  C'mon Jack... Please! :)

[deleted]

>   ARexx will be forthcoming in the 1.1 release of JR-Comm.  How about some
> suggestions on what you'd like to see in an ARexx port?  E-mail please..

Access to ALL the menu items via AREXX, would be numero uno. Ability to
change/specify the name of the AREXX port would be another.

I use JRCOMM .94 on occasions, but not very often. It would be cute to see it
with an Arexx interface.

Dac
--
 _l _  _   // Andrew Clayton. Canberra, Australia.         I Post  .
(_](_l(_ \X/  Send mail to dac@prolix.pub.uu.oz.au                . .  I am.