Hi Tony, Yes there are workarounds. For example in Python you import a module when you need it and by default they are not in access. In TW we can use import variable pragma whenever we needs the macro and we can remove $:/tags/Macro
But all of these do not let the clean, less error prone route I proposed. I am not sure may be there is another solution in TW. --Mohammad On Friday, August 30, 2019 at 12:23:20 PM UTC+4:30, TonyM wrote: > > Mohammad, > > I believe there are sufficient workarounds that are less complex to manage > than you are proposing. > > You could have macros in a tiddler and simply transclude them at the top > of the tiddler or in a conditional transclude by the ViewTemplate. If the > same macros are global and defined elsewhere they will be overwritten with > your transcluded macros. For example you could use a tiddler-type field and > include a specific macro set only for particular tiddler-types. > > You could tag your macros and only include those with a particular tag. > > The dumpvariables Macro is helpful with this kind of work and the > new variables Operator can allow you to test if a variable exists and if > not do something including transclude a tiddler containing "local macros". > > If you wanted you could have in each tiddler a transclude-macros-list > field that if present will transclude the named tiddlers containing the > local macros (may need some backend work). > > Regards > Tony > > > > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/874bf40a-9465-484e-b706-f1fe4fbc122f%40googlegroups.com.
