CB>  What I would like is my QWK/REPs automatcially be sent/fetched
CB>  to my mail directory.  Gifs, PCX, etc. be sent to my picture
CB>  dir, ZIPs, Arcs, etc. be sent to my normal download dir and so
CB>  on.

Carey,

        I have 4 strew directories in CS-MAC ... mail (qwk, etc)
downloads, pictures (gif, jpg, etc), archives (zip, arc, etc) and a
second mail directory (zns and sou).  What other strew categories
would you like to see?  I'm not being a smart-aleck, I add what
users ask for ... these are the only four directories that I thought
of while writing the strew routine.

        BTW, the strew routine in CS-MAC allows you to download to a
non-empty directory (like your download directory) and after logoff,
it moves (if necessary) the files to their desired homes.

CB>  And using a batch file wouldn't help get my REPs out my mail
CB>  directory.

        CS-MAC detects upload packets and automatically sends (then
deletes) them.  Upload packets may be in the same directory as
downloaded mail, or in their own directory .. you specify your
chosen reply directory during an initial configuration process.

CB>  It [the Commo macro language] doesn't allow numeric variables
CB>  so you can't have 'for' loops etc.

        Oh!  But Commo does have numeric variables and numeric
variable operators (incr, decr, mult, and divi).  I have quite a
number of "for" loops in my macros!  An example is building a menu
on the fly that reads variables of the form "menu_item#" with #
being a number.  The menu is built by reading menu_item1, then 2,
then 3, and so on until menu_itemX is NUL .. indicating that it's
time to show the menu.

        Another quick "for" loop shows the number of seconds until
exiting Commo and updating the display once a second until the count
reaches zero (with abilty to abort the exit during the count-down).

CB>  It seems a bit restrictive to limit it to two macro files at a
CB>  time when most others can automatically call any number of
CB>  routines in others.

        The CS-MAC series is six macros.  One is the "home" macro
and it never is removed from memory.  The second position is
occupied by whichever macro file holds the called routine.  This is
a very flexible arrangement and provides for unlimited growth.  If
you can't get a certain task done with 64k of macro language, then
it is a daunting task indeed .

CB>  The free form nature of the settings and fone directory and
CB>  macro file defintly take a bit of getting used to.

        Aye, that it does.  But once you are accustomed to having
commands enclosed in curley braces, it is a very convenient and
forgiving structure to comment.

CB>  Also it being restricted to 1 line seems restrictive.  Maybe
CB>  you should add a 'continuation' indicator like Fortran had.

        In the FON directory I agree completely.  I have some FON
entries that are closing in on the 255 character limit.  Your
suggestion here is excellent!  In the macro files this isn't much of
a problem, since it is tough to come up with a 255 character macro
command.

CB>  Telix does have the most extensive macro language that I've
CB>  seen (sorry Fred), but I just don't like HAVING to write macros
CB>  to do things that I feel should be possible directly from the
CB>  dialing dir.

        I'll disagree with the comparison of Telix and Commo macro
language.  I think Commo is at least as powerful as Telix.  Well, if
Telix can open more than one file handle at a time for reading (or
writing) then I'll concede ... but Commo has loads of programming
horsepower.  I feel justified in making that statement because I
have been able to deliver a macro to perform EVERY function I have
ever seen requested by a Commo user.

        Along those lines, you don't have to personally compose
macros ... I am very impressed by the following that Commo has
earned ... by looking and asking you will find that most macros you
wish for have already been composed.  Commo macros are very
available.

CB>  Commo does have fairly decent online help. (Not as extensive as
CB>  some, but decent.)  Unlike Telemate or Telix. (The telix people
CB>  (Zack Jones & Jeff Woods) were totaly baffled as to why I would
CB>  want online help to be more than just a quick key reference.)

        I have the "home" key assigned to call up Commo complete
documentaion for those times that the F1 help isn't sufficient.
"Home" uses LIST to read *.DOC ... and LIST has handy string search
facilities to help me find the command or subject that I need to
reference.

        Let me make a couple of closing comments.  Your insightful
comments inspire me to make useful additions to my personal macros.
I hope you continue to give Commo a good workout and that you
continue to share your thoughts with the Commo community.  Thank you!

04/17/95   23:03                                        ChuckùS
---
 þ JABBER v1.3á1 #á021 þ Toad: what happens to an illegally parked frog.

---------------