Grüß Dich, mark!
Am 27 Jun 15, mark lewis schrieb an Kai Richter:
KR>> group can be one single echotag, which matches your example in
KR>> the easiest way. group can be a wildcarded echotag, to match all
KR>> REQUEST.* echos or NODES.* or ALLFIX* or BBS* and so on.
ml> interesting... i don't know why i would want to do that but it is
ml> cool...
You could use different mail template to have more detailed footer with system
information in special echos and sub-echos. But i see...
ml> now, if there was a way to select different tagline files based on
ml> the group, that might be interesting ;)
...you found one. ;)
GROUP GED:
MEMBER GOLDED.GER
MEMBER GOLDBETA.GER
XLATEXPORT IBMPC
; TAGLINESUPPORT yes
; TAGLINE @golded.tag
; ORIGIN @~/tpls/origin/default.origin
ENDGROUP
Group based charset definition is one of the more useful things...
Tschuess
Kai
--- GoldED+/LNX 1.1.4.7
* Origin: Monobox migrating to Linux (2:240/1351.7)
|