Hi..
 CB> Well, I like to have seperate capture files for each BBS and for
 CB> them to automatically open (append) when I connect.  I'm sure it
 CB> could be done by macros, but, well, I don't like writing macros.
 CB> It's odd since I'm a hobbiest programmer and know Pascal, C,
 CB> Fortran, and even Forth.
Yes, what you want to do could be done very easily with a small (very!)
macro.  Something on the order of:
{:1st}
  {:capt y,%capdir%%nodeid.cap}{}
..then just routinely set "nodeid" via an entry in your .FON directory,
with "{1st}" in the linked macro field.
 CB> What I would like is my QWK/REPs automatcially be sent/fetched to
 CB> my mail directory.  Gifs, PCX, etc.  be sent to my picture dir,
 CB> ZIPs, Arcs, etc.  be sent to my normal download dir and so on.
While this is possible right now using a custom macro, I think it's also
an excellent idea for something Fred could add to the internal
offerings.  Conceivably, it could be something similar to the {aut=}
startup string series.  For example, perhaps there could be a series of
temp_dirs available in the .SET file.  Maybe something like:
        {abc=GIF,c:\picture}
        {abc=QWK,c:\mail}
        .
        .
        {abc=ZIP,c:\files}
With the "abc" variable usable in the protocol command lines as the
target directory, e.g., "{RZMO %abc}".
Any non-specified extension would be sent to the default download
directory.  Fred already knows how to get the filename during the
transfer (after all, it's in the protocol status window), so I assume
it's "do-able" to grab the extension.
 CB> Also, I think auto upload would be nice.  Especially for REP
 CB> packets.
That's been possible for quite a while.  But, yep, it means fiddling
with macros again.
 CB> The free form nature of the settings and fone directory and macro
 CB> file defintly take a bit of getting used to.
Personally, I find this characteristic a huge plus over other comm
programs.  I really enjoy the ease/speed at which I can make changes
using my favorite text editor, without having to rely upon some unique
utility which is associated with the comm program.  Plus, it's nice not
having to convert phone directories, etc., every time a new version of
the program comes out.  I remember having to do that a few times in my
pre-{COMMO} days.
 CB> I don't like writing macros.
Then {COMMO} probably isn't for you.  One of the reasons I like {COMMO}
so much is that it doesn't try to be all things to all people in the
default version, like some other programs..only to turn out to be a
bloated program that doesn't do anything really well, just a bunch of
stuff partially well.  Instead, the macro language enables the user to
customize his/her version as much/little as they need.  It's this
flexibility that was the original drawing card for me.  I like being
responsible for adding the bells & whistles I want, rather than having
to suffer through all the other bells & whistles the author thinks a lot
of people may want.
Regards..
Jim
                                                                
--- Maximus/2 2.02
---------------