Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macros should not be identified using the $:/tags/macro tag #2

Open
AnthonyMuscio opened this issue Mar 23, 2019 · 2 comments
Open

Comments

@AnthonyMuscio
Copy link

Mohammad,

Macros should not be identified using the $:/tags/macro tag because someone may want to store a macro an include it when required rather than make it global. If they remove the tag is is not longer considered a macro?

If the existing syntax field was altered to macro-syntax you could search for tiddlers with a macro-syntax field prefix, however sometimes there is by nature more than one usable macro in a single tiddler. For example a submacro that can be used in its own right, this would not work. This is why I favored a field macro-macroname containing the syntax, thus one tiddler can have more than one macro and the description can be generalised a little.

Regards
Tony

@AnthonyMuscio
Copy link
Author

My mistake you are using title. Never the less my comments still stand.

@kookma
Copy link
Contributor

kookma commented Mar 23, 2019

@AnthonyMuscio
As it is described, Yazd is a KISS collection. So, if a macro is usable by itself, it should be stored in a dedicated tiddler. Here by sub-macro I mean a macro that is not usable!

Regarding the tag, I agree with you! So, I can remove the tag $:/tags/Macro. In my opinion if we could have library and import selected macro on demand it would be great!

--Mohammad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants