1. Forum
  2. FidoNet
  3. GOLDED

  • XLAT

    From Karel Kral@2:423/39 to All on Sunday, January 09, 2022 09:43:04
    Hello All!

    Is there any easy way how to have more configurations depens on conference? For example: in worldwide echo GOLDED to use different CHRS kludge than in GOLDED.42 (national one)?

    Karel

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Plast DATA (2:423/39)
  • From Michiel van der Vlist@2:280/5555 to Karel Kral on Sunday, January 09, 2022 13:40:20
    Hello Karel,

    On Sunday January 09 2022 09:43, you wrote to All:

    Is there any easy way how to have more configurations depens on conference? For example: in worldwide echo GOLDED to use different
    CHRS kludge than in GOLDED.42 (national one)?

    Simply call it with a different config file as first parameter.

    gedwin -goldrus.cfg.

    But I use groups to do this:

    GROUP Dutch
    member bnl.algemeen
    member HOLLAND.SYSOP
    member points.028
    TEMPLATE DUTCH.TPL
    TAGLINESUPPORT yes
    TAGLINE @dutch.tag
    xlatexport CP850
    ENDGROUP

    GROUP LATIN
    member LOCALTEST
    member FTSC_PUBLIC
    member fidonews
    member NETMAIL001
    xlatexport LATIN-1
    ENDGROUP

    GROUP UTF8
    xlatimport utf-8
    member UTF-8
    member TEST.5555 FTSC GOLDED
    dispsoftcr no
    xlatexport UTF-8
    origin Deputy Nodelist Police
    ENDGROUP


    Hope this helps.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: http://www.vlist.eu (2:280/5555)
  • From Kai Richter@2:240/77 to Karel Kral on Thursday, January 13, 2022 16:30:18
    Hello Karel!

    09 Jan 22, Karel Kral wrote to All:

    Is there any easy way how to have more configurations depens on conference? For example: in worldwide echo GOLDED to use different
    CHRS kludge than in GOLDED.42 (national one)?

    Yes, the group and member keywords you have seen already are part of the so called random system. Refer to the docs for details.

    You don't need a second cfg file. You can use the group/member keywords in your normal config - just make sure they are written after the area definition.

    And you can use wildcards, e.g. to catch all national echos
    member *.42

    First match counts.

    Make sure you have a final member * group to catch the common defaults.

    Regards

    Kai

    --- GoldED+/LNX 1.1.4.7
    * Origin: Monobox (2:240/77)