qbit: I think you are using it wrong. This form of a transclusion is a "template" {{||ThingStuff}}
eg:
Let's say you have a tiddler named: test
. eg: If you want to show the "description" field within the test-tiddler you can do this: {{test!!description}}
. Since you are already "in" the test-tiddler you can use the "shorthand" instead: {{!!description}}
. ... So {{!!description}}
internally uses the <<currentTiddler>>
variable for the missing tiddler name. ... In the context of the test-tiddler text the <<currentTiddler>>
variable is set to "test"
If you transclude: {{myText}}, it will show the content of the "myText" tiddler within the test-tiddler. If you use {{!!description}} in the "myText" tiddler it will show the description-field form myText and not the description from test-tiddler. The <<currentTiddler>>
variable with "{{myText}}" is set to "myText"
If you use {{||myText}}
in the test-tiddler, it will keep the <<currentTiddler>>
variable at "test" ... So if you use {{!!description}}
in the "myText" tiddler it will show the "description field" of the "test" tiddler. ... So {{||myText}}
is called a template-tiddler.
pmario: that’s how I am using them, but I was hoping I could also transclude the literal field names into the new tiddler.
Basically I want to auto populate a new tiddler’s field set (the literal list of fields, not the values from the template) from a transcluded tiddler
Yea, I thought about that as I did read your posts. ... Fields don't "stack" :). ... What you can do is using the <$tiddler />
widget. eg:
title: test
description: test - test
Transclude the "local" description field: {{!!description}}
<$tiddler tiddler="myText">
Transclude the "myText" description field: {{!!description}}
</$tiddler>
YYYY-0MM-0DD
[sameday:schedule[<currentTiddler>search-replace:g[-],[]]]
[sameday:schedule[20210816]]
schedule[]
part?
You cannot nest things like that. Especially you should remember you cannot have "another pair of square brackets inside a another one" except the initial first pair. Sorry, that sounds more confusing than it is, but you can't nest them like that. You must "export" such logic into variables and then use those. Here is a working example of what you want to do
<$vars thedate={{{ [<currentTiddler>search-replace:g[-],[]] }}}>
{{{ [sameday:schedule<thedate>] }}}
</$vars>
I tested this by creating a tiddler named 2021-08-16
and put the "code" in the tiddler body. While I had created another tiddler with any name but with a field schedule
with value of 20210816
and it worked. Good luck!
<$vars thedate={{{ [<currentTiddler>search-replace:g[-],[]] }}} >
{{{ [sameday:schedule<thedate>] }}}
</$vars>
I think the code snippet broke so I am sending it again.
https://tiddlywiki.com/#TiddlerFiles
Well, you can import/export multiple tiddlers using ".json" format. But you still have to import them manually. The other format like that contain a single tiddler like .tid may also work but you'll still have to manually import them all in a bulk (via drag and drop at the top part of the Tiddlywiki in browser because the import button which brings a window doesn't allow multiple selection) and it should work.
Alternatively, if you want everything automated. After making a json file that looks like the json TiddlyWiki can export, you may try to construct a TiddlyWiki using node.js commands.
<$list filter="[{!!name}addsuffix[-additional]]" > <$transclude mode="block"/></$list>
).<<tabs "[tag[listForTabs]!sort[title]]" """$:/state/tab" "tc-vertical">>
. Here's where the problem occurs- the fields that I've referenced and the transclusion via list are not visible, so the tabs have names, but show up with blanks in them. Is there a way that I can get the fields that I've referenced and transclusions to 'stick' wherever it will be shown within the tabs?
Without reproducing your setup fully. I want to tell you about the fact that within a tabs macro, the variable <<currentTiddler>>
points to the Tiddler that contains the tab macro itself, not the ones aggregated by the tags. This is why with {!!name}
it tries to find it on the tiddler with the tab macros on. Not the Tiddler that is the tab.
Saying this just in case due to ambiguity, but If you are storing the same tiddler title in a field name
that's may not be needed?, because transcluding {{!!title}}
or <<currentTiddler>>
(or within a filter step {!!title}
and <currentTiddler>
even all[current]
) will produce the tiddler name. Which you may be able to use. In that case, it may be sufficient to replace those with another variable provided by the tabs macro called <<currentTab>>
(or <currentTab>
for filter notation)
More information about <<currentTiddler>>
problem and <<currentTab>>
and its existance can be read here (at the bottom of this tiddler): https://tiddlywiki.com/#tabs%20Macro
Either way, those were side notes from me.
Your solution that you are looking for, should be this. Wrap your list widget with the workaround from the link.
<$tiddler tiddler=<<currentTab>>>
<$list filter="[{!!name}addsuffix[-additional]]" > <$transclude mode="block"/></$list>
</$tiddler>
However, saving a folder directly to github as .tid ... I am not sure about that?
That's not possible with the GitHub saver.
and I believe that TiddlyWiki.com is using git separately to commit and push it to a github repository when needed (not as part of seemless editing? but I can be wrong)
That's right. tiddlywiki.com wiki is built with: https://github.com/Jermolene/TiddlyWiki5/blob/master/bin/build-site.sh and then pushed to https://github.com/Jermolene/jermolene.github.io which contains the gh-pages