JD;
Thank you, amazing theme. I am playing with it a lot. I particularly like
the display of the last 10 days when the storyriver is empty. This is very
usefull. I am trying to modify this so that rather than the display the
last ten days it would show a particular tag that I selected say from
*Feature in Tiddlywiki 5.1.23*
TW 5.123 has a new filter operator called cycle
https://tiddlywiki.com/prerelease/#cycle%20Operator
Using this filter operator it is simple to build a button to cycle in your
color palettes!
See the how to in new *Show and tell* page of GitHub Discussion board.
On Saturday, December 12, 2020 at 9:38:46 PM UTC-8 taale...@gmail.com wrote:
> Thanks Eric! That works - except not in the caption field. Still get the
> recursion error. I think waiting until v23 is out will have to do.
> Do we have an ETA yet?
>
"very soon"... in the meantime, you can
Thanks Eric! That works - except not in the caption field. Still get the
recursion error. I think waiting until v23 is out will have to do.
Do we have an ETA yet?
On Sat, Dec 12, 2020 at 9:41 PM Eric Shulman wrote:
> On Saturday, December 12, 2020 at 7:40:44 PM UTC-8 taale...@gmail.com
>
On Saturday, December 12, 2020 at 7:40:44 PM UTC-8 taale...@gmail.com wrote:
> Uncaught RangeError: Maximum call stack size exceeded
>
This error is indicative of a run-away recursion. Without digging into the
code myself, I'm not sure why this is the case. In any event, I suggest
entirely
Well, that's not quite the solution after all, because I keep getting this
error:
Uncaught RangeError: Maximum call stack size exceeded
I don't have issues with the macro on tiddlywiki.com, so I don't know what
I'm doing wrong. Can anyone figure out what's wrong?
I'm using the macro in the
This thread has what I
needed: https://www.mail-archive.com/tiddlywiki@googlegroups.com/msg91214.html
On Thursday, December 10, 2020 at 6:19:09 PM UTC-7 Eric Shulman wrote:
> On Thursday, December 10, 2020 at 5:05:04 PM UTC-8 saq.i...@gmail.com
> wrote:
>
>> There is a pad[] filter operator
Mark S,
This might be a good basis for further development: import into the
prerelease, enter a filter in the Advanced Filter
([!is[system]search[saver]] for example) and press the "Export as Zip"
button next to it.
https://groups.google.com/g/tiddlywiki/c/5NhT_i1NUxA/m/2a0ttv2SAQAJ
Mark S.
Wow, Thanks, Eric!
For book references, it works straightaway! For more general use, this part
would need tweaking:
removeprefix[@book
The "book" part is actually important in the bibtex system, since it
belongs in the type-field.
Of course, filling in the type field manually isn't
I see , thanks! that is a much better method to implement the idea
Mark S. 在 2020年12月12日 星期六下午8:53:02 [UTC] 的信中寫道：
> I suspect your usage would break the spirit of the JS rules, since it's
> using a macro to change TW content.
>
> But you could write a non-JS (i.e.wikitext) macro that would
I suspect your usage would break the spirit of the JS rules, since it's
using a macro to change TW content.
But you could write a non-JS (i.e.wikitext) macro that would basically do
the same thing. If the tiddler doesn't exist, it would show a button which,
when clicked on, would create the
odin...@gmail.com, danraymond, TiddlyTweeter,
Sorry for the late fix, I hope it works well now. All you have to do is
import this tiddler into your own wikis (click on "Export tiddler" from the
dropdown menu and drop the file to your wikis) to get the fix included:
I wish to implement the following functionality, using JS macro, defining
the macro with name M.
Whenever I use a macro <> , then it creates
a Tiddler with title "New Tiddler". Then the macro presents this link [[New
Tiddler]]. The point is that the macro will create the Tiddler for me (with
Hi Maki
iSH is a bit of a hack: it essentially uses an x86 emulator to run Linux as a
way to get around the app store rules, and so performance and compatibility are
both poor.
Both Play.js and JSBox support Node.js apps, but the difference is that JSBox
also offers a rich API for creating
I don't own any apple products, but looking over google, I see that Apple
started requiring all apps to use https back in 2016. I wonder if using
http could be the problem?
On Saturday, December 12, 2020 at 8:31:46 AM UTC-8 ma...@makiaea.org wrote:
> happy to be back using tiddlywiki! i
Hi Jan,
Happy to hear it helped. I have to say, I was expecting you to post a QR
code rather than a link ;)
Cheers,
Saq
--
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
Hi Saq, hi Tones!
Saq your solution works great!
Sorry for not answering earlier...I could not get it to work at first
because the join-opperator needed a newer version.
Having updated I can report success.
It is a button to call a modal with a QR code linking to the current
Tiddler ... and
@TT we are in agreement. While Dev discussions on GH are a good move, I
already feel the need to manage those notifications better and would not
want to clutter them further with non-development related discussions.
On Saturday, December 12, 2020 at 3:44:00 PM UTC+1 TiddlyTweeter wrote:
> Ciao
Ciao Saq
Got it! Agreed!
Just want to post resistance to any idea arising everything should go
GitHub!
TiddlyWikiDev on GG is being retired in favour (correctly) of GH.
This group isn't & any idea it should makes no sense.
Best wishes
TT
On Saturday, 12 December 2020 at 15:36:12 UTC+1
"For the context that won't help a lot UNLESS general discussion is Dev
highly relevant."
@TT my comment is meant to facilitate separating the *Dev* discussions on
Github from Issues and PRs. I would expect Issues and PRs to be of greater
urgency, and hence would sort them differently in my
Ciao Mohammad
We should make clear that we talking about discussion ANYWHERE on GitHub,
not just in the TW repository.
I DO think its a route to start development support for many aspects of TW
real usage. *For instance* I would love a special Dev context to
collaborate on POWERSHELL script
Hello community.
I am fascinated by the trick http://about.bitty.site/ can do, which was
shared some time ago in this group.
I would like to do a plugin and code a php-backend which can do this
directly from TW.
To make it efficient, the data would have to be compressed before
turning it into a
But Saq.
For the context that won't help a lot UNLESS general discussion is Dev
highly relevant.
As far as I can see the general discussion group--vital to end users--is
NOT dominantly about development of TW.
Its about optimizing usage. I find it hard to see how GH is relevant to
that need.
Hello and welcome to the tiddlyverse!
I can't answer your area conversion question in terms of getting javascript
running but I can point you to
https://github.com/joshuafontany/TiddlyWikiFormula
which lets you do that kind of thin natively in tiddlywiki.
For example I've done a forces
Jeremy: check the CC field of the discussion notification emails to see if
there is something to filter them by.
https://docs.github.com/en/free-pro-team@latest/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications
On Saturday,
Cioa si
... it would be nice to find an approach that has fewer steps.
>
Its an interesting question which could be answered several ways.
In my own case I use TWs that have access to the OS via launching Windows
batch files (supported in Bob, the previous version of Timmimi saver,
One thing I've discovered is that it when GitHub sends a notification email it
is not possible to distinguish discussion posts from issues. That's pretty
catastrophic for me because I usually triage things via filters in email. So
from a core development team perspective I definitely wouldn't
Ciao Jeremy
GitHub’s mission is focussed on developers, a very different audience than
> TiddlyWiki.
>
Right. Actually GitHub Discussions ARE (I been using it) pretty easy to
understand and contribute to.
GitHub Discussions might make sense for the Dev group but I worry that the
> whole
addendum:
> <$vars f={{{ [split[={]first[]trim[,]trim[]] }}} v={{{
> [split[={]rest[]trim[,]trim[]] }}}>
>
Note that these inline filters use the enhanced trim[...] operator
available in soon to be released TW5.1.23
-e
--
You received this message because you are subscribed to the
On Friday, December 11, 2020 at 4:45:33 PM UTC-8 springer wrote:
> drag and drop the contents of a field-parsable string (onto a special
> bibtex or json drop area if need be) and have tiddlywiki parse directly,
> populating fields if field patterns are present?
>
Try this:
\define
See https://github.com/Jermolene/TiddlyWiki5/issues/5261#issue-763431242
On Saturday, December 12, 2020 at 10:44:10 AM UTC+3:30 saq.i...@gmail.com
wrote:
> @springer So the dropzone widget which handles the import/paste/drag
> actually lets you specify how to interpret the incoming text.
>
>
31 matches
Mail list logo
