Mario,
First I made a mistake and tried to use
\import
Is there a reason we cant use the same mechanisium?
Regardless I did use
\importcustom {{mytablecode}}
and it works well, it also helps limit the applicability while allowing
re-usability.
In the same vein would it be possible to tag such a tiddler
with $:/tags/Macro or similar to make them global?
- No need to protect the user from redefinition's etc.. style-sheets and
existing macros already permit this, it is even safe to call it a feature!
- Perhaps we need to make clear what in a customise pragma will result
in redefinition occurring if customised a second time.
- Eg the tick=name
In the previous reply on widgets
> I wonder if we could toggle this "Undefined widget " message off, when
> not debugging, on by default.
>
I understand it is a core feature, I just ask if it may be of value to
raise an issue?, does it's opening to arbitrary widget names, introduce the
ability for "custom markup" to customise, the widget name used, in effect
to disable that widget.
Regards
Tony
> pragmas _can't_ be transcluded. \importcustom .. seems to have a problem
> atm. It only works if you do
>
> \importcustom [[tiddler with pragmas]]
>
> \customize tick=asdf use=<symbol defined in "tiddler with pragmas">
>
> ´asdf some text should work.
>
> If you only have
>
> \importcustom [[tiddler with pragmas]]
>
> ´asdf some text should work.
>
> It doesn't work atm. .... but it should.
>
> -mario
>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/tiddlywikidev/3457f4c4-2ccc-4be7-af81-29a3a886306ao%40googlegroups.com.
