Subj : linkOption logic?
To   : Kai Richter
From : Oli
Date : Sat Feb 19 2022 07:33 pm

Kai wrote (2022-02-19):

 KR> Hello All!

 KR> When i look to the logic for the echoarea definition -nm switch i found:

 KR> ##############################################################################
 KR> #EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions]
 KR> #
 KR> # LinkOptions:
 KR> #  -mn
 KR> #    this link is mandatory subscribed,
 KR> #    you may also set:
 KR> #       "<aka> -r -mn"
 KR> #    or
 KR> #       "<aka> -w -r"
 KR> #    and so on...

 KR> Because there may be links that have a read-only or write-only (-r -w)
 KR> limitation this linkOption works per individual linkAKA?


 KR> If yes i'd like to suggest a documentation update from:

 KR> #EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions]
 KR> to
 KR> #EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs [linkOptions]]

Which is not different at all. Do you mean something like this:

#EchoArea <name> <file> [-b <msgbase>] [Options] [link1_AKA [linkOptions]] [link2_AKA [linkOptions]] ...

---
 * Origin: They're made out of meta (2:280/464.47)

.