PR> As far as I know, yes.  If you're running the stock COMMO.MAC,
PR> you could just copy the new one over it.  I generally work as a
PR> cut/paster with all "my stuff" at the head end of the macro, and
PR> all "Fred's stuff" after it.
DS> Are you saying that the stuff that comes FIRST in the macro-file is
DS> what is used?  And the same macros later re-defined get ignored?
DS> Shouldn't that be the other way 'round?
DS> If I assign A=7, but later A=9, then the final result is A=9.
DS> Why would A still equal 7?  How can I EVER change the value of A
DS> then?
PR> No, I didn't say anything like that.  I try not to "step on"
PR> Fred's values in "my stuff".  
I don't see anything wrong with "stepping on" Fred's values.
I thought that was the whole purpose of a very configuratable program...
Fred can have his values, we can change them (or leave them as-is) as need 
.
I'll ask directly...
Which takes precedence if I have a certain thing configed twice (to different 
values)?
The first instance, or the second?
I wanted to leave Fred's values in place (for reference purposes) (or in case 
I need to later "undo" my changes).  And then just *ADD* mine in there too.  
But should they go BEFORE Fred's or AFTER?
--- CNet/3
---------------