date:20210418

On Saturday, April 17, 2021 at 1:01:06 AM UTC+2 rayv...@gmail.com wrote:
...

> I use this filter below to have overview of a day, i put the date in 
> manually, must be possible to do that better but ok it works for me:
>

If you put this into a tiddler, it will give you a list of tiddlers, that 
have been created the same Year / Month / Day / hour ... as this tiddler. 

\define sameYear() 
\define sameMonth() 0MM
\define sameDay() 0MM0DD
\define sameHour() 0MM0DD0hh

<$set name=thatDate filter="[get[created]format:dateaddprefix[^]]">
<sort[created]]" 
emptyMessage:"n/a">>

<$set name=thatDate filter="[get[created]format:date<
sameYear>addprefix[^]]">
<sort[created]]" 
emptyMessage:"n/a">>

The problem with such a filter function in a Journal tiddler is, that: 
"What if I did create the journal tiddler 1 day late". ... So I want to 
date it back, which isn't possible with the created field. ... 

So your approach with manually setting the value is probably the right one, 
but it may be simplified. eg: 

\define thatDate() ^20210418

<sort[created]]" 
emptyMessage:"n/a">>

The ^ char is needed, because it means "at the start of the line" ... eg if 
you use 2021 without the ^ it could find a tiddler with the time 20:21

have fun!
mario

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c8c660c1-ed72-4247-9486-3150de2a8f4fn%40googlegroups.com.

Re: [tw5] Re: The simplest way to include the JS code into Tiddlywiki

2021-04-18 Thread Flibbles

I know I'm a little late to the party here, but I think your first solution 
may not have worked because it didn't have a module-type. If you have...

module-type: utils

...then tiddlywiki will load this tiddler on startup (and put any existing 
exports int utils, which will be none). As it is, tiddlywiki won't touch 
your tiddler. You have it specified as javascript, but tiddlywiki has no 
reason to believe it should compile it yet.

On Sunday, April 18, 2021 at 12:52:06 AM UTC-4 Mohammad wrote:

> Thank you Mark!
>
> I will give a try!
>
>
>
> Best wishes
> Mohammad
>
>
> On Sun, Apr 18, 2021 at 8:44 AM 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com> wrote:
>
>> In that case, thanks to Brian's input, I seem to have gotten it to work, 
>> though maybe only once. Here's a screen shot without the code:
>>
>> [image: 1618718712_2105_17.04.2021_1366x768.png]
>>
>> and here's a screenshot with the code
>>
>> [image: 1618718788_2106_17.04.2021_1366x768.png]
>>
>> I only tested once. For about 3 seconds. I have no idea if it breaks with 
>> repeated use, as  Brian suggested.
>>
>> Good luck!
>>
>>
>> On Saturday, April 17, 2021 at 8:55:35 PM UTC-7 Mohammad wrote:
>>
>>> On Sun, Apr 18, 2021 at 1:18 AM 'Mark S.' via TiddlyWiki <
>>> tiddl...@googlegroups.com> wrote:
>>>
 Hi Mohammad,

 How do you test your code? On a small device? Portrait mode? Or ... ?

>>>
>>> Hi Mark, 
>>> I used the code on a large screen (laptop)! I attached the three 
>>> tiddlers show to the JS, CSS and the test!
>>> To examine the code you need to add/remove some text to push the tooltip 
>>> to the edge of the screen!
>>>

 -- 
>> 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 tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/280af977-1b60-4b87-a154-27d91a0393b1n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/ff334b94-c767-4e99-bbec-aed95407ec4dn%40googlegroups.com.

[tw5] Re: Subfilter recursion

Update, I did another experiment and subfilter[] does work the way you were 
using it. I'm guessing Mark is right and it tries to create the filter 
before it actually runs it and sees there are no results.

On Sunday, April 18, 2021 at 2:36:33 PM UTC-5 Soren Bjornstad wrote:

> I've never tried to do a recursive* filter*, so I don't know what's 
> technically possible (though I've never seen someone try to use multiple 
> filter runs in *subfilter* and am a bit suspicious that the second run is 
> doing a tagging[] on everything in your wiki). But recursive macros are 
> easy and functional, and I suspect they'll work for your use case. Here's 
> one version that does an outline of the TOC on tiddlywiki.com, using the 
> current tiddler to easily pass the state through to the next level:
>
> \define recurse()
> <$list filter="[all[current]tagging[]]">
>   <>
>   <>
> 
> \end
>
> <$tiddler tiddler="TableOfContents">
>   
> <>
>   
> 
>
> On Sunday, April 18, 2021 at 2:01:51 PM UTC-5 Yaisog Bonegnasher wrote:
>
>> Hi,
>> I recently tried to create a recursive subfilter to find all tiddlers 
>> below a certain tag, no matter how many levels deep (similar to the *kin* 
>> filter, which  is too slow for my large wiki). Unfortunately, I was greeted 
>> with a red-message-box-of-death informing me of too much recursion. 
>> However, there should only be a couple of levels.
>> Are recursive filters at all possible or am I doing something wrong?
>> For a quick example, try this in a new tiddler on tiddlywiki.com:
>> \define subfilter-test() [tagging[]] [tagging[]subfilter]
>>
>> <$set name="test" filter="[[TableOfContents]subfilter]">
>>   <$list filter="=[enlist]" template="$:/core/ui/ListItemTemplate" 
>> />
>> 
>> Any enlightment is greatly appreciated.
>> Best regards
>> Yaisog
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/435419d8-6c41-4f5c-b8f8-15b0f2aa210cn%40googlegroups.com.

[tw5] Re: Subfilter recursion

I've never tried to do a recursive* filter*, so I don't know what's 
technically possible (though I've never seen someone try to use multiple 
filter runs in *subfilter* and am a bit suspicious that the second run is 
doing a tagging[] on everything in your wiki). But recursive macros are 
easy and functional, and I suspect they'll work for your use case. Here's 
one version that does an outline of the TOC on tiddlywiki.com, using the 
current tiddler to easily pass the state through to the next level:

\define recurse()
<$list filter="[all[current]tagging[]]">
  <>
  <>

\end

<$tiddler tiddler="TableOfContents">

<>

On Sunday, April 18, 2021 at 2:01:51 PM UTC-5 Yaisog Bonegnasher wrote:

> Hi,
> I recently tried to create a recursive subfilter to find all tiddlers 
> below a certain tag, no matter how many levels deep (similar to the *kin* 
> filter, which  is too slow for my large wiki). Unfortunately, I was greeted 
> with a red-message-box-of-death informing me of too much recursion. 
> However, there should only be a couple of levels.
> Are recursive filters at all possible or am I doing something wrong?
> For a quick example, try this in a new tiddler on tiddlywiki.com:
> \define subfilter-test() [tagging[]] [tagging[]subfilter]
>
> <$set name="test" filter="[[TableOfContents]subfilter]">
>   <$list filter="=[enlist]" template="$:/core/ui/ListItemTemplate" />
> 
> Any enlightment is greatly appreciated.
> Best regards
> Yaisog
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0a8b1534-1ee3-43dd-a8d5-56dc9fee230cn%40googlegroups.com.

[tw5] Re: Subfilter recursion

2021-04-18 Thread 'Mark S.' via TiddlyWiki

My guess is that it's trying to build the complete filter even before it 
runs, so that's why you hit the recursive limit. That is, it's not running 
one filter, running the next, testing, etc. It's trying to build the whole 
thing, which has no way of exiting.

Since you know about how many levels, maybe you could prevent the over-run 
like this:

\define subfilter-test5() [tagging[]] [tagging[]]
\define subfilter-test4() [tagging[]] [tagging[]subfilter]
\define subfilter-test3() [tagging[]] [tagging[]subfilter]
\define subfilter-test2() [tagging[]] [tagging[]subfilter]
\define subfilter-test()  [tagging[]] [tagging[]subfilter]

<$set name="test" filter="[[HelloThere]subfilter]">
  <$list filter="=[enlist]" template="$:/core/ui/ListItemTemplate" />


You can add on as many levels as you think you'll ever need. 

On Sunday, April 18, 2021 at 12:01:51 PM UTC-7 Yaisog Bonegnasher wrote:

> Hi,
> I recently tried to create a recursive subfilter to find all tiddlers 
> below a certain tag, no matter how many levels deep (similar to the *kin* 
> filter, which  is too slow for my large wiki). Unfortunately, I was greeted 
> with a red-message-box-of-death informing me of too much recursion. 
> However, there should only be a couple of levels.
> Are recursive filters at all possible or am I doing something wrong?
> For a quick example, try this in a new tiddler on tiddlywiki.com:
> \define subfilter-test() [tagging[]] [tagging[]subfilter]
>
> <$set name="test" filter="[[TableOfContents]subfilter]">
>   <$list filter="=[enlist]" template="$:/core/ui/ListItemTemplate" />
> 
> Any enlightment is greatly appreciated.
> Best regards
> Yaisog
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/132fb0c1-8067-4e8b-ac93-0c0887b1cf8an%40googlegroups.com.

Re: [tw5] Mentat

2021-04-18 Thread Jan Johannpeter

Hi Ray,
I recall that the Tiddlers have to be tagged to behave in the mentat or
volant mode.

Cheers
Jan

Am Sa, 17. Apr, 2021 um 3:29 VORMITTAGS schrieb Ray Vermey
:

Hi,

i installed the great looking all the Mentat plugins and it looks
really nice.

I drag and resize, works nice!
But when i create a new Tiddler it is shown behind the tiddlers on
screen.

Is that on purpose?
I must close all the other tiddlers to reach the new one.
Am i using the wrong workflow here??

Also the red Engine button is hidden under the Google Drive button...
That is a bit annoying... is a placement option for 1 of the 2
possible?

Also when i edit a tiddler the top of it is underneath the Topbar of
Mentat.

That makes it a bit difficult to close..

I feel i use it the wrong way, can someone tell me how i can make the
best use

of it?

Thanks

Ray
--
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 tiddlywiki+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/c6144b7c-2f43-4f62-ba89-a2f139523b45n%40googlegroups.com
.

--
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/X4YRRQ.7SK8QTAGO7ZW1%40gmail.com.

[tw5] Re: A tour through my Zettelkasten

The filter that pulls the snippet stops when it reaches the first period, 
question mark, or exclamation mark, so that it only pulls the sentence 
after the TODO. In your case, you have a link to youtu.be within the first 
sentence, so when it hits the . after 'youtu', it stops, and the result 
isn't valid wikitext. If you wanted to have a different way of indicating 
where the TODO ended so you can have more freedom in what you put in the 
snippet, you could adjust the *splitre *accordingly.

On Sunday, April 18, 2021 at 1:05:54 PM UTC-5 ludwa6 wrote:

> Ah, nice: that's got it working. Nifty affordance, that!  
>
> Now as it happens: this reveals to me another curious thing (what you 
> might have covered in the video, Soren; if so i apologise. So much detail 
> in that to master!): following standard wikitext notation, i embedded that 
> link to your video above, i.e.- [[Soren's video at 28'47"|
> https://youtu.be/GjpjE5pMZMI?t=1727]] -in a topical tiddler flagged with 
> [[TODO]] on that line.  The link shows up & works as it should in the 
> source tiddler... But then where it gets transcluded by the TODO tiddler, 
> it shows up like this- *TODO:* See if i can get this working as indicated 
> [[in Soren's video at 28'47"|https://youtu.-with a little padlock icon 
> that i can't reproduce here inserted right after the pipe, just before that 
> truncated URL, which doesn't work when clicked, of course.  What's up w/ 
> that, i wonder?
>
> /walt
>
>
> On Sunday, April 18, 2021 at 4:55:35 PM UTC+1 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]].
>>
>> 
>> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>>   <$list 
>> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>>  
>> variable=inner>
>>   <$link to=<>/>
>> ''TODO:'' <>.
>> 
>> 
>> 
>>
>> ...
>>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/dd9a0d48-70b7-4e5e-897c-ad22d2ddacb3n%40googlegroups.com.

[tw5] Subfilter recursion

2021-04-18 Thread Yaisog Bonegnasher

Hi,
I recently tried to create a recursive subfilter to find all tiddlers below 
a certain tag, no matter how many levels deep (similar to the *kin* filter, 
which  is too slow for my large wiki). Unfortunately, I was greeted with a 
red-message-box-of-death informing me of too much recursion. However, there 
should only be a couple of levels.
Are recursive filters at all possible or am I doing something wrong?
For a quick example, try this in a new tiddler on tiddlywiki.com:
\define subfilter-test() [tagging[]] [tagging[]subfilter]

<$set name="test" filter="[[TableOfContents]subfilter]">
  <$list filter="=[enlist]" template="$:/core/ui/ListItemTemplate" />

Any enlightment is greatly appreciated.
Best regards
Yaisog

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/14ff56e5-cdb1-4fc5-9c73-d328828acab2n%40googlegroups.com.

[tw5] Re: One journal tiddler / day (like a diary): how?

On Sunday, April 18, 2021 at 8:06:40 PM UTC+2 rayv...@gmail.com wrote:

> ?? I don't understand the problem.

The OP says: " How can I change the "new journal" button to bring up that 
day's journal entry (creating it if necessary)?!
The PR can handle this.

The OP says: (Optional:) How can I arrange that on creating a new tiddler 
it gets appended to that day's journal's list? 
IMO the PR can handle this, if you click "New Journal" and then "New 
Journal Here". ... It's just a different workflow

> What is wrong with creating a new Journal Tiddler for every action, event, 
> "thing", happening during the (work)day and use tags like i do?
>

There is nothing wrong, it's just a bit different than described in the OP. 

-mario

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c3a4d568-6ac5-473e-a2b8-2ae403df2f14n%40googlegroups.com.

[tw5] Re: One journal tiddler / day (like a diary): how?

2021-04-18 Thread Ray Vermey

?? I don't understand the problem.
What is wrong with creating a new Journal Tiddler for every action, event, 
"thing", happening during the (work)day and use tags like i do?
What am i missing??

Ray

Op zondag 18 april 2021 om 19:45:06 UTC+2 schreef PMario:

> Hi, 
> I did create a PR at github: 
> https://github.com/Jermolene/TiddlyWiki5/pull/5614
>
> The repo also contains a link to an *experimental wiki, *that is for 
> tests only!!!
>
> Read the comments on the PR and vote +1 if you want to have this function 
> in the core. 
>
> have fun!
> mario
>
>
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/2a6bc58e-c95a-4f80-b205-eeb2d9e5ff2cn%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

Ah, nice: that's got it working. Nifty affordance, that!  

Now as it happens: this reveals to me another curious thing (what you might 
have covered in the video, Soren; if so i apologise. So much detail in that 
to master!): following standard wikitext notation, i embedded that link to 
your video above, i.e.- [[Soren's video at 
28'47"|https://youtu.be/GjpjE5pMZMI?t=1727]] -in a topical tiddler flagged 
with [[TODO]] on that line.  The link shows up & works as it should in the 
source tiddler... But then where it gets transcluded by the TODO tiddler, 
it shows up like this- *TODO:* See if i can get this working as indicated 
[[in Soren's video at 28'47"|https://youtu.-with a little padlock icon that 
i can't reproduce here inserted right after the pipe, just before that 
truncated URL, which doesn't work when clicked, of course.  What's up w/ 
that, i wonder?

/walt

On Sunday, April 18, 2021 at 4:55:35 PM UTC+1 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]].
>
> 
> <$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
>   <$list 
> filter="[get[text]splitregexplast[]splitregexpfirst[]]"
>  
> variable=inner>
>   <$link to=<>/>
> ''TODO:'' <>.
> 
> 
> 
>
> ...
>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/979322ef-c627-4041-9fe3-1623ee5651e0n%40googlegroups.com.

[tw5] PR for new functionality for New Journals and New Journals Here is active.

 Hi folks, 

I did just create a PR at github: 
https://github.com/Jermolene/TiddlyWiki5/pull/5614

The repo also contains a link to an *experimental wiki, *that is for tests 
only!!!

Read the comments on the PR and vote +1 if you want to have this function 
in the core. 

The PR was inspired by: 
https://groups.google.com/g/tiddlywiki/c/KyNX1E6Hjn4 and I also wanted this 
function for quite some time already

have fun!
mario

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/1b0e7595-f8ad-45bf-bcd7-e07447a5432en%40googlegroups.com.

[tw5] Re: One journal tiddler / day (like a diary): how?

Hi, 
I did create a PR at github: 
https://github.com/Jermolene/TiddlyWiki5/pull/5614

The repo also contains a link to an *experimental wiki, *that is for tests 
only!!!

Read the comments on the PR and vote +1 if you want to have this function 
in the core. 

have fun!
mario


-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/017aae4a-a912-4227-88bd-513af5a7d8a4n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

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]].


<$list filter="[[TODO]backlinks[]] -[[TODO]]" variable=outer>
  <$list 
filter="[get[text]splitregexplast[]splitregexpfirst[]]" 
variable=inner>
  <$link to=<>/>
''TODO:'' <>.




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" 
>  : "*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  : 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/4f12dac0-b621-436f-be03-169eb4d1e878n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

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" 
 : "*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  : 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/48aec381-d411-409f-93bc-12d6943d670en%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

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  : 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9528cd62-a66c-4299-b57a-1d9b9b0b3895n%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

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  : 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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/378cafb6-53c4-4df4-b56c-073c7e50c81an%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten

Minor correction: in the list of setup steps (second code block from the 
bottom), add this line at the end:

mkdir wiki

On Sunday, April 18, 2021 at 7:35:05 AM UTC-5 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.
>
> Wherever you keep your wiki, your folder tree should look like this:
>
> My Zettelkasten
> |- zk-wiki
> |- public-wiki
> |- scripts
>|- publish.sh
>
> ...where publish.sh is the script below, and public-wiki is an empty 
> folder that your public wiki will be built into. If you don't like 
> "zk-wiki" or "public-wiki" as names, you can change them in the constants 
> block just below.
>
> #!/bin/bash
>
> ### Change these constants to taste. (Don't remove the quotation marks at 
> the beginning and end of any value.) ###
> PRIV_FOLDER="zk-wiki"
> PUB_FOLDER="public-wiki"
> FILT='[is[system]] [tag[Public]] -[[$:/plugins/tiddlywiki/tiddlyweb]] 
> -[[$:/plugins/tiddlywiki/filesystem]] -[prefix[$:/temp]] 
> -[prefix[$:/state]] -[prefix[$:/sib/StorySaver/saved]] 
> +[!field:title[$:/sib/WriteSideBar]]'
> WIKI_NAME="index.html"
> ext_image_folder="extimage"
>
> ### Various sanity checks to ensure we're able to start building the wiki 
> without breaking anything. ###
> pub_wiki="${PUB_FOLDER:?eek}/wiki"
> pub_ghpages="${PUB_FOLDER:?eek}/pages"
>
> die() {
> ret=$?
> printf "%s\\n" "$@" >&2
> exit $ret
> }
>
> cd "$(dirname "$0")/.." || die "Script in unexpected location. Please 
> check script."
> [ -f "package.json" ] || die "cd to project root failed. Please check 
> script."
>
>
> ### Do the build. ###
> echo "Exporting public tiddlers..."
> rm -rf "$pub_wiki"
> "$(npm bin)/tiddlywiki" "$PRIV_FOLDER" --savewikifolder "$pub_wiki" "$FILT"
>
> echo "Externalizing images..."
> "$(npm bin)/tiddlywiki" "$pub_wiki" --savetiddlers "[is[image]]" 
> "$ext_image_folder"
> # Note: images are saved here but aren't replaced with references until 
> next command.
>
> echo "Compiling single HTML file..."
> "$(npm bin)/tiddlywiki" "$pub_wiki" \
> --setfield "[is[image]]" _canonical_uri 
> '$:/core/templates/canonical-uri-external-image' text/plain \
> --setfield "[is[image]]" text "" text/plain \
> --render "$:/core/save/all" "$WIKI_NAME" text/plain
> cp -r "$pub_wiki/output"/* "$pub_ghpages"
>
>
> ### Publish built wiki to the web. ###
> if [ "$1" = "--push" ]; then
> echo "Pushing compiled wiki to GitHub..."
> cd "$pub_ghpages" || exit 1
> git add .
> git commit -m "publish checkpoint"
> git push
> else
> echo "Not pushing the wiki to GitHub because the --push switch was not 
> provided."
> fi
>
> Once you have this file created, go into your *My Zettelkasten* folder, 
> open Git Bash, and type the following to make your script executable and 
> clone your GitHub Pages repository to a location where the script can find 
> it:
>
> chmod +x scripts/publish.sh
> mkdir public-wiki
> cd public-wiki
> git clone https://your/repository/clone/url pages
>
> After initial setup, whenever you want to publish, you just start Git Bash 
> in the *My Zettelkasten* folder and say:
>
> scripts/publish.sh --push
>
> On Sunday, April 18, 2021 at 5:54:03 AM UTC-5 ludwa6 wrote:
>
>> Cool -editor works fine now- so i've make this my personal github.io repo 
>> , where i'll try to document my journey of 
>> learning with Zettelkasten as i go.  Have not yet found a good way to 
>> export just the Public (i.e. not tagged "private") tiddlers for push to 
>> Github; was kinda hoping the standard "export all" tool might serve for 
>> that purpose,  but it seems not.  If anyone can suggest a good low-friction 
>> workflow for this (ideally w/o any command line voodoo involved :-), i'd be 
>> much obliged!
>>
>> /walt
>>
>> On Sunday, April 18, 2021 at 12:18:53 AM UTC+1 Soren Bjornstad wrote:
>>
>>> Haha, sorry, I forgot to turn off the vim keybindings. PMario has 
>>> explained how to do that.
>>>
>>> On Saturday, April 17, 2021 at 1:30:57 PM UTC-5 ludwa6 wrote:
>>>
>> OK, after struggling w/ this a bit, i have to stop and ask: is there 
 something that would cause the editor widget to behave very differently 
 from standard TW5?...
>>>
>>>
 On Saturday, April 17, 2021 at 6:06:29 PM UTC+1

[tw5] Re: A tour through my Zettelkasten

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.

Wherever you keep your wiki, your folder tree should look like this:

My Zettelkasten
|- zk-wiki
|- public-wiki
|- scripts
   |- publish.sh

...where publish.sh is the script below, and public-wiki is an empty folder 
that your public wiki will be built into. If you don't like "zk-wiki" or 
"public-wiki" as names, you can change them in the constants block just 
below.

#!/bin/bash

### Change these constants to taste. (Don't remove the quotation marks at 
the beginning and end of any value.) ###
PRIV_FOLDER="zk-wiki"
PUB_FOLDER="public-wiki"
FILT='[is[system]] [tag[Public]] -[[$:/plugins/tiddlywiki/tiddlyweb]] 
-[[$:/plugins/tiddlywiki/filesystem]] -[prefix[$:/temp]] 
-[prefix[$:/state]] -[prefix[$:/sib/StorySaver/saved]] 
+[!field:title[$:/sib/WriteSideBar]]'
WIKI_NAME="index.html"
ext_image_folder="extimage"

### Various sanity checks to ensure we're able to start building the wiki 
without breaking anything. ###
pub_wiki="${PUB_FOLDER:?eek}/wiki"
pub_ghpages="${PUB_FOLDER:?eek}/pages"

die() {
ret=$?
printf "%s\\n" "$@" >&2
exit $ret
}

cd "$(dirname "$0")/.." || die "Script in unexpected location. Please check 
script."
[ -f "package.json" ] || die "cd to project root failed. Please check 
script."

### Do the build. ###
echo "Exporting public tiddlers..."
rm -rf "$pub_wiki"
"$(npm bin)/tiddlywiki" "$PRIV_FOLDER" --savewikifolder "$pub_wiki" "$FILT"

echo "Externalizing images..."
"$(npm bin)/tiddlywiki" "$pub_wiki" --savetiddlers "[is[image]]" 
"$ext_image_folder"
# Note: images are saved here but aren't replaced with references until 
next command.

echo "Compiling single HTML file..."
"$(npm bin)/tiddlywiki" "$pub_wiki" \
--setfield "[is[image]]" _canonical_uri 
'$:/core/templates/canonical-uri-external-image' text/plain \
--setfield "[is[image]]" text "" text/plain \
--render "$:/core/save/all" "$WIKI_NAME" text/plain
cp -r "$pub_wiki/output"/* "$pub_ghpages"

### Publish built wiki to the web. ###
if [ "$1" = "--push" ]; then
echo "Pushing compiled wiki to GitHub..."
cd "$pub_ghpages" || exit 1
git add .
git commit -m "publish checkpoint"
git push
else
echo "Not pushing the wiki to GitHub because the --push switch was not 
provided."
fi

Once you have this file created, go into your *My Zettelkasten* folder, 
open Git Bash, and type the following to make your script executable and 
clone your GitHub Pages repository to a location where the script can find 
it:

chmod +x scripts/publish.sh
mkdir public-wiki
cd public-wiki
git clone https://your/repository/clone/url pages

After initial setup, whenever you want to publish, you just start Git Bash 
in the *My Zettelkasten* folder and say:

scripts/publish.sh --push

On Sunday, April 18, 2021 at 5:54:03 AM UTC-5 ludwa6 wrote:

> Cool -editor works fine now- so i've make this my personal github.io repo 
> , where i'll try to document my journey of 
> learning with Zettelkasten as i go.  Have not yet found a good way to 
> export just the Public (i.e. not tagged "private") tiddlers for push to 
> Github; was kinda hoping the standard "export all" tool might serve for 
> that purpose,  but it seems not.  If anyone can suggest a good low-friction 
> workflow for this (ideally w/o any command line voodoo involved :-), i'd be 
> much obliged!
>
> /walt
>
> On Sunday, April 18, 2021 at 12:18:53 AM UTC+1 Soren Bjornstad wrote:
>
>> Haha, sorry, I forgot to turn off the vim keybindings. PMario has 
>> explained how to do that.
>>
>> On Saturday, April 17, 2021 at 1:30:57 PM UTC-5 ludwa6 wrote:
>>
> OK, after struggling w/ this a bit, i have to stop and ask: is there 
>>> something that would cause the editor widget to behave very differently 
>>> from standard TW5?...
>>
>>
>>> On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:
>>>
>> The public version lacks some functionality that is important for editing 
 and has a bunch of settings changed that are a bit of a pain to change 
 back, so it'll be much better if I do a second build off of the "real" 
 private version. I've attached a first 15-minute attempt at this.

 Things that could use improvement here:

- There are

[tw5] Re: A tour through my Zettelkasten

Cool -editor works fine now- so i've make this my personal github.io repo 
, where i'll try to document my journey of 
learning with Zettelkasten as i go.  Have not yet found a good way to 
export just the Public (i.e. not tagged "private") tiddlers for push to 
Github; was kinda hoping the standard "export all" tool might serve for 
that purpose,  but it seems not.  If anyone can suggest a good low-friction 
workflow for this (ideally w/o any command line voodoo involved :-), i'd be 
much obliged!

/walt

On Sunday, April 18, 2021 at 12:18:53 AM UTC+1 Soren Bjornstad wrote:

> Haha, sorry, I forgot to turn off the vim keybindings. PMario has 
> explained how to do that.
>
> On Saturday, April 17, 2021 at 1:30:57 PM UTC-5 ludwa6 wrote:
>
>> OK, after struggling w/ this a bit, i have to stop and ask: is there 
>> something that would cause the editor widget to behave very differently 
>> from standard TW5?...
>> On Saturday, April 17, 2021 at 6:06:29 PM UTC+1 Soren Bjornstad wrote:
>>
>>> The public version lacks some functionality that is important for 
>>> editing and has a bunch of settings changed that are a bit of a pain to 
>>> change back, so it'll be much better if I do a second build off of the 
>>> "real" private version. I've attached a first 15-minute attempt at this.
>>>
>>> Things that could use improvement here:
>>>
>>>- There are no instructions at all, so you'll have to figure out how 
>>>to get started on your own. Some of the conventions tiddlers are missing 
>>>and would be nice to have.
>>>- I included all the red, yellow, and black tag tiddlers, but since 
>>>there is no content in this version, most of them are not tagging 
>>> anything, 
>>>so they don't show up in the tags list. Also, some of the tag tiddlers 
>>> have 
>>>content that probably won't be very useful for you in them.
>>>- There's a button for the ReadingInbox on the toolbar, but said 
>>>inbox is not included in the edition at present. You can hide or delete 
>>>that button tiddler.
>>>
>>> Please let me know what else does not work right – I'd love to add a 
>>> build of this edition to my standard publish process in the future
>>>
>>

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/052d4c56-d70b-4eda-a9b6-b25b85e87d97n%40googlegroups.com.

[tw5] Re: One journal tiddler / day (like a diary): how?

Hi David,

You pointed out an oversight in the configuration possibilities, that 
doesn't work for your workflow. ... 

We do have a "New Journal" button in the right sidebar, which by default 
creates 1 tiddler per day. ... That's OK. 

We also have a "New Journal Here" button in the tiddler toolbar, that will 
automatically tag the new journal with the actual tiddler title. ... That's 
OK. ... BUT this "New Journal Here" button uses the same title 
configuration as "New Journal" ... That's a problem. 

In your case "New Journal" should be: [UTC]-0MM-0DDZ ... and
"New Journal Here" should be: [UTC]-0MM-0DD 0hh:0mm:0ssZ   ... Which 
needs a new field in the control panel

I wanted to send a fast hack, with some changed UI tiddlers, but I did find 
a bigger problem with the "New Journal Here" button, that imo should be 
fixed in the core. 

So I'll create a pull-request, that should make it easier for users, with 
your workflow. 

have fun!
mario

-- 
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 tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/0100bbb8-d1a2-4e88-9dc9-688385ccfccan%40googlegroups.com.

[tw5] Re: A tour through my Zettelkasten