Use = as synonym for : in macro/procedure calls?

Developers
#1

Is there a tecnical or logical reason we can’t

Use = as synonym for : in macro/procedure calls?

For example

\procedure has-parent(title-filter:"[<currentTiddler>!is[system]]" symbol:"↫" separator:" | " level-symbol:↫")

Restated as

\procedure has-parent(title-filter="[<currentTiddler>!is[system]]" symbol="↫" separator=" | " level-symbol="↫")

At a surface level I see no reason this would be a problem, but it would stop a reoccuring error on my part, especialy now $transclude variable name. parameters widget and other features mean I use the = more often now.

1 Like
#2

If possible, I’d also like to have this option (and its converse) in macrocall/transclude widgets! I’ve regularly “broken” a piece of code by switching from e.g. <<tabs tabsList:"A B C">> to <$macrocall $name=tabs tabsList="A B C" /> and forgetting to change that pesky tabsList:" to tabsList=".

2 Likes