Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    GOLDED    |    GoldED Public Release discussion.    |    2,690 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 566 of 2,690    |
|    Kai Richter to mark lewis    |
|    Golded+ and QWK    |
|    27 Jun 15 04:52:24    |
      Tag auch mark!              Am 26 Jun 15, mark lewis schrieb an Kai Richter:               KR>> The random system chooses between two given origin definitions        KR>> randomly. What would happen if the is one origin definition only?        KR>> What would happen if there is one username definition only?               ml> see? the name "random" just implies some automatic choice using a        ml> selector to choose from more than one option...              That matches the function exactly. But "automatic choice" "selector" is the       group match in the list of groups. ;)               KR>> group pdq        KR>> username "another name"        KR>> endgroup               KR>> would do your wish. xyz and pdq must be exact echotags and be        KR>> before other wildcarded echotags. In the random system the first        KR>> hit counts.               ml> echotags? not groups??              The random system is very powerful and can handle "groups" in many ways.              Like Nick posted it can be groups by letters, as used in fidoconfig       definitions (i didn't knew that before, ty). This affects all echos which are       part of the group as defined in fidoconfig.              group can be one single echotag, which matches your example in the easiest way.       group can be a wildcarded echotag, to match all REQUEST.* echos or NODES.* or       ALLFIX* or BBS* and so on.              group can be a so far unknown unique groupname and echos can be included into       this new group with the MEMBER keyword. As far as i know "member" can use       wildcards too. The trick is that it's valid to use more than one member       keyword. You could build a group with same defaults for all ALLFIX*, BBS* and       OS2* echos for example.               ml> why is it called "group" then?              Because the group and endgroup keywords are used to build groups in many ways.               ml> i have my echotags grouped for similar items... eg: group z is my        ml> automatically added areas... it is at the bottom of the list... group        ml> a is my local areas... group b is fidonet backbone carried areas... i        ml> also break out administrative areas into their own groups... these        ml> groups are the same as the groups the tosser uses...              If it works, that's great! ;-)              My next step should be international templates and origin lines, but i'm to       lazy at the moment.              Tschuess              Kai              --- GoldED+/LNX 1.1.4.7        * Origin: Sag mir wo die Blumen sind, wo sind sie geblieben... (2:240/1351.7)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca