Thank you Jeremy.
--
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 post to this group, send email to
Hi Mark,
> I was looking at the each code to see if I could make an "each string"
> macro. It turns out that there is an undocumented feature in the *each*
> filter. A list like this:
>
> <$list filter="[has[veld]regexps:veld[(C\d\d\d)]each:value[title]sort[]]"
> variable="code">
>
> May do
Hi Talha
> On 16 Jul 2018, at 17:14, talha131 wrote:
>
> Excise is a useful for all types of content type. What should I do to enable
> it for all content type? Or is it a bug?
I’m afraid it is a bug, already fixed for 5.1.18 here:
My personal opinion and experience is the save / setup piece definitely
hurts adoption, but use-case less so.
Coming from a non-technical, Windows background, if I was running
TiddlyWiki, I'd develop my landing page towards:
- Web first: Start with a sign-up to get you into a TiddlySpot
Stranger,
before I embarked on Tiddlywiki some years ago, meaning investing time,
money, resources in it and before entrusting my data to this software, I
asked myself the same question.
So I did some extensive research, on Jeremy Ruston, but also on the
members of the core team.
My
Alex,
I will just add in your example, to use the TOC macros, you will need a
root tag, such as TableOfContents or in your case maybe "AllCategories"
that tags Category A and Category B then the TOCs root tag will be
AllCategories
Regards
Tony
On Tuesday, July 17, 2018 at 12:16:07 AM
Stobot has put into words very clearly what I had in the back of my mind.
Name
Name is definitely an issue. A long time ago I mentioned TiddlyWiki Classic
to my coworkers and all I get laughs. In those days when JS wasn’t as
ubiquitous as it is today, a whole wiki system enclosed in a single
Dear Pit.W.
Thank you for the useful reply.
The Stranger.
--
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 post to
Josiah,
I suppose my own journey from TiddlyWiki Classic is an example of TW being
off putting, Every time I looked at TW5 I got confused. I must admit
looking back at what feature came in which version I see now it was not so
mature back then. So is it much more mature now?, yes, it is as a
Talha,
In relation to your syntax question, jeremy explained it well, but we need
to help new people learn this early. The reason <<>> is used as in
<> and <> is used in wikitext is to not compete with
so when you are inside a widget we need not keep up
this << >> and we fall back to < >
I heard good things about Mr Ruston. Before I tempt the waters of TW I'd
like to know more about him.
--
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
Hi, I've been thinking about this (using Org-mode and TW as
mutually-beneficial systems), and I suspect that Org is a poor means of
approaching TW's concerns regarding hypertext. With that said, I think that
the combination of them both can be useful and easier done than you might
be
Hello all,
my question is probably a no-brainer for you folks, but I am totally
overwhelmed
:-(
I have the following construct of tiddlers:
- category-tiddler, not tagged
- list-tiddler, tagged with a category
- task-tiddler, tagged with a list
I now want a nested (dynamic)
Thanks a lot, I will have a look into it!!
Am Montag, 16. Juli 2018 15:56:54 UTC+2 schrieb Mark S.:
>
> The table-of-content macros can already do that for you:
>
> https://tiddlywiki.com/#Table-of-Contents%20Macros
>
> Have fun,
>
> -- Mark
>
> On Monday, July 16, 2018 at 5:40:57 AM UTC-7, Alex
I'm trying to create tiddler that will act as a form for new tiddlers.
I want to have an edit-widget that will pass on the title to a new tiddler.
I also want to use a select-widget to choose among a list of tiddlers with
the tag "Scene" to use as the tag for the new tiddler.
So far I have
The table-of-content macros can already do that for you:
https://tiddlywiki.com/#Table-of-Contents%20Macros
Have fun,
-- Mark
On Monday, July 16, 2018 at 5:40:57 AM UTC-7, Alex W wrote:
>
> Hello all,
>
> my question is probably a no-brainer for you folks, but I am totally
> overwhelmed
>
It's a bit convoluted because the tags need to be added with the tm-add-tag
message after the new tiddler is created. This seems to work:
\define makenewtiddler()
<$action-createtiddler $basetitle={{UseMeAsName}} $savetitle=
"NewTiddlerName" />
<$fieldmangler
Thanks Jed, this enlist solution is perfect for my needs. I was looking for
exactly the same format.
the interface between javascript and the much *maligned widgets* can be a
bit complex because the widgets are designed to make markup tasks simple.
Haha, seems like there is a fault line in
Hi Mark,
Your solution using the each filter operator works great.
The disadvantage of creating (empty) tiddlers is not that important to me.
My 4 MB TW contains already about 1800 tiddlers and not all series of
'codes' contain doubles. In practice it means I need to have about 100
tiddlers
I strikes me often that we now give so many ways to save and use TW that
its actually off-putting.
Let me qualify that. Off-putting for an end-user looking for a decent
"text-base."
On the one hand we have all the methods. On the other hand we have users
looking for the minimal way forward.
I have fixed the issue to the best of my knowledge and opened up a pull
request at Github
https://github.com/Jermolene/TiddlyWiki5/pull/3360
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving
Stop the presses!
I was looking at the each code to see if I could make an "each string"
macro. It turns out that there is an undocumented feature in the *each*
filter. A list like this:
<$list filter="[has[veld]regexps:veld[(C\d\d\d)]each:value[title]sort[]]"
variable="code">
May do what
I am using TW version 5.1.17 on NodeJS. I have noticed as soon as I set
content type to wiki or markdown, the button disappears.
When content type is not set
When content type is set
Excise is a useful for all types of content type. What should I do to
enable it for all content type? Or is
Dear Sirs,
Since January, I've been using the Documents App in iOS (iPhone and iPad)
to read the Tiddlywiki files.
In this application, you can sync an entire folder with Tiddlywiki files
and sub-embed-files (pdfs and images), and you can access the content
without problems. It is a kind of
24 matches
Mail list logo
