Probably did, but right now that one is more or less just <<list-links "[[OpenQuestion]backlinks[]]">> -- there's no special functionality for selecting questions out of the tiddlers. That's something I'd like to improve in the future.
On Monday, June 28, 2021 at 12:12:30 PM UTC-5 [email protected] wrote: > Is there any chance your filter missed the OpenQuestions tiddler as well? > > On Sunday, April 18, 2021 at 11:55:35 AM UTC-4 Soren Bjornstad wrote: > >> Looks like my filter missed the TODO tiddler, which should contain: >> >> \define todore() \[\[TODO\]\]: >> \define splitre() [\.\?!] >> >> To add a TODO item to this list, simply link to [[TODO]]. >> >> <dl> >> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer> >> <$list >> filter="[<outer>get[text]splitregexp<todore>last[]splitregexp<splitre>first[]]" >> >> variable=inner> >> <dt><$link to=<<outer>>/></dt> >> <dd>''TODO:'' <<inner>>.</dd> >> </$list> >> </$list> >> </dl> >> >> On Sunday, April 18, 2021 at 10:23:28 AM UTC-5 ludwa6 wrote: >> >>> Good to know, Soren, but first i have to get the basics under control, >>> like: TODO items! >>> >>> About that, you say in your video at 28'47" >>> <https://youtu.be/GjpjE5pMZMI?t=1727> : "*Anywhere that i write the >>> word todo in square brackets, so link to the tiddler todo, gets >>> automatically pulled in here"* -here being presumably TODO tab of >>> "Write" feature, since that is the context. I have tried this a number of >>> ways -with square brackets of both types: single (would have to be by some >>> magic i don't see, but since you didn't say "DOUBLE"...) and double >>> (creating a missing tiddler, which i then activated, tagged "Stub"), >>> whether as TODO uppercase or lower... Nothing shows up as expected in that >>> tab, at all. >>> >>> So what am i missing here, i wonder? >>> >>> /walt >>> >>> On Sunday, April 18, 2021 at 3:31:11 PM UTC+1 Soren Bjornstad wrote: >>> >>>> Oh, to convert a single-file wiki to Node.js, all you need is: >>>> >>>> tiddlywiki --load path/to/single/file.html --savewikifolder >>>> path/to/output/folder >>>> >>>> You could even do this as a first step in the script above, if you >>>> wanted to normally edit in single-file mode but use the automated build. >>>> >>>> On Sunday, April 18, 2021 at 9:02:28 AM UTC-5 ludwa6 wrote: >>>> >>>>> Thank-you Soren, but to be clear: I'm working in single-file mode, >>>>> since i was unable to find a way to convert your file to node.js, though >>>>> that would probably make for a more elegant solution [*]... But the >>>>> "manual" method you propose below (with slight adaptation, see below) is >>>>> sufficiently well-automated, it makes my workflow relatively painless, as >>>>> follows: >>>>> >>>>> 1. In TiddlyDesktop (where i am managing a fair mitt-full of TW5 >>>>> instances), finish my days edits with a review to ensure tag "Public" >>>>> is on >>>>> all the right tiddlers, and none other; >>>>> 2. In $:/AdvancedSearch, run the filter- >>>>> [tag[Public]!is[system]] -and upload the result set as .json, to... >>>>> 3. Drag & drop that .json file into the my local PUBLIC instance >>>>> (subset of the above), which is they synced to... >>>>> 4. My github.io repo <https://ludwa6.github.io/> : pull from there >>>>> (just to ensure there are no conflicting edits), then >>>>> commit/comment/push >>>>> changes online. >>>>> >>>>> NB: I'm using Atom text editor (on Mac, b/t/w, not Windows) for the >>>>> last step, just because i like its change management workflow, but >>>>> there's >>>>> a desktop app for Github that is probably the most intuitive GuI app for >>>>> this purpose. >>>>> >>>>> [*] As to that more elegant solution: if it were a node.js instance i >>>>> had in github, then i can see how it might be easier to manage a dataflow >>>>> based on individual tiddlers, instead of one big .html file -especially >>>>> if >>>>> others were to be engaged in collaborative editing (via Github Pull >>>>> Request)... But that's a bridge too far for me to even think about at >>>>> this >>>>> point. Gotta play with this for a while first IMCST (In My Copious Spare >>>>> Time -ha!), in the hope that it will at some point save me more time than >>>>> it costs me to manage it -the most important question to ask of any >>>>> database app, i guess, yes? >>>>> >>>>> /walt >>>>> >>>>> >>>>> On Sunday, April 18, 2021 at 1:35:05 PM UTC+1 Soren Bjornstad wrote: >>>>> >>>>>> A manual option would be to go to $:/AdvancedSearch, type in the >>>>>> filter you want to export (e.g., [tag[Public]] [is[system]]), use the >>>>>> export button to the right of the search box to export as JSON, and then >>>>>> import that JSON file into a fresh empty.html and publish that HTML file. >>>>>> >>>>>> That said, since you are already using Node.js, automating this with >>>>>> "command-line voodoo" isn't that hard, and then it will do everything >>>>>> for >>>>>> you with one command, without a chance of making mistakes. Here's a >>>>>> simplified version of what I use. I'm guessing you're using Windows, but >>>>>> if >>>>>> so and you have github.io set up, you probably already have Git for >>>>>> Windows installed, which will be enough to run a Bash script like the >>>>>> one >>>>>> below. Mac/Linux will run this script out of the box.... >>>>>> >>>>> -- 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/d1e25e68-31c5-4b9d-9546-a3b53c8f375en%40googlegroups.com.
