Thanks for your suggestions. nice tips
is it possible to evaluate and insert today’s date? [<now YYYY0MM0DD>] i couldn’t figure out a working solution just now, maybe i’m missing something obvious?
For me it worked
Suggestion Filter: [all[tiddlers]!sort[modified]limit[1]get[modified]format:date[0DD-0MM-YY 0hh:0mm]]
Display Filter:
[<currentTiddler>]
Template:
" d:$option$ "
3 Likes
A slight modification to @vyug18’s idea:
Suggestion filter: [<editedTiddler>get[modified]format:date[YYYY0MM0DD]] – should be slightly more performant, if you only need date, not time. I takes the modified date time of the current draft, so unless you start editing before midnight and insert timestamp after, it will be correct I guess.
Here is a complete trigger tiddler, ready to use, with trigger ddd:
$__EvidentlyCube_Trigger_CurrentDate.json (397 Bytes)
Edit: the modified field of the <editedTiddler> seems to be updated all the time on every edit to the draft, not just upon creating the draft. So this solution works also if one needs time in their timestamp.
1 Like
For this, I would absolutely go with Dynamic Rubber Stam by @Mark_S. I believe for this use case rubber stamp is more suitable and AutoComplete use case is different.
1 Like
thank you all very much @vyug18 @vilc @Mohammad ! i went with @vyug18 's solution as it was most appropriate for my needs on mobile; i tried to make it a wiki article but could not find a way to move it to a more appropriate place (tips & tricks?) thanks again, it’s really helped my workflow!
2 Likes
Life has its way of being annoying and taking you away from the important things.
Version 1.0.18 is out:
- Fixed RSOD in TW 5.3.0+ caused by new API not being supported
- Fixed RSOD when earlier keyup causes the focus to be changed – can be triggered by setting
sidebar-searchshortcut to the same key as manually triggering auto complete.
@Scribs The first part fixes the issue you reported here – this was caused by internal API changes introduced in TW 5.3.0
@vilc The second part fixes the issue you reported here – this was caused by the Sidebar Search shortcut having higher priority, which would cause focus to be lost, which would reset some variables (but not all) which was the source of the issue. It just gracefully cleans itself, I don’t believe there is a way for me to prevent the Sidebar shortcut (nor I am confident I’d like to do it anyway). Don’t share your shortcuts! 
4 Likes
@Maurycy I have found an inconsistency. I’m not sure it’s a bug, since I don’t know if this feature is supposed to be supported. And there’s an easy alternative in my use case anyway.
I need to use the regexp operator with a regular expression containing the character class/ range [a-z] in its parameter. In this case the the parameter cannot be literal regexp[[a-z]].
I tried the solution indicated in TW docs, that is to use a variable. I defined a global macro (tagged with both $:/tags/Macro and $:/tags/Global just in case) with the regex.
Using regexp<myMacro> (just a part of the filter ofc) yields this strange result:
- “Test the filter” table in the trigger config shows proper results (in my case all titles starting with lowercase, by using regex
^[a-z]) - Using the filter “in the wild”, it looks like the macro simply doesn’t work/ evaulates to nothing, or as if
regexp[]was used.
I ended up using a data tiddler regexp{dataTiddler##property} and it works well everywhere. Same with field transclusion regexp{tiddlerWithFields!!field}.
Just wanted to let know. It’s not actually a problem for me, since I found the alternatives.
Edit: I’m using TW v5.3.1 and AC v1.0.18
1 Like
Whoops. That’s both a bug and expected behavior. The completion API runs with a faux base widget so it has no access to globally defined macros and variables, done mostly for simplicity of the codebase than for any other particular reason.
This should be fixed at some point for sure and I’ll take a note of this problem but no promises when this gets fixed. Glad you’ve got a good workaround!
I don’t know how I went this long without knowing this plugin existed. I needed this so bad I was considering making something like this myself.
As a community, TiddlyWiki really needs to work harder at improving plugin visibility.
4 Likes