[tw5] Re: Building a list of tabs dynamically in a performant manner

[Saq Imtiaz]

Hi Soren, I mentioned this when I suggested the filter and explained in a 
bit more detail in  a follow up reply which seems to never have been posted.

 You will need the 5.2.0 pre-release for that filter to work, as one of the 
changes is greater consistency in setting the value of currentTiddler for 
:filter, :reduce and :sort and their operator equivalents.  
See  https://tiddlywiki.com/prerelease/#Filter%20Expression

On Friday, July 23, 2021 at 2:17:24 AM UTC+2 Soren Bjornstad wrote:

> Tones, thanks for putting this together, but your solution is slower than 
> mine as far as I can tell (no easy way to instrument that since it has a 
> very different number of filters, but the difference is apparent from 
> clicking around a bit).
>
> Saq, I can't get your filter to work and I can't see how it would work in 
> theory either now that I look at it – the !!condition in the subfilter is 
> getting the condition field on the tiddler in which the tab list is being 
> rendered, whereas it needs to be the *tab* tiddler that's coming in on 
> the input of the subfilter operator…right? Or am I just being dense? In my 
> :reduce version it has a different meaning because :reduce actually 
> resets the currentTiddler variable to match the input value currently being 
> processed .
>
> With the additional optimization work I did the other night, including 
> optimizing the filters on each tab as Saq pointed out, I would say it's now 
> performing acceptably with my current version, if only barely on a slower 
> computer. So if nobody has any other ideas, I think I can leave it where it 
> is for now.
>
>
> On Wednesday, July 21, 2021 at 8:58:05 AM UTC-5 TW Tones wrote:
>
>> Oops;
>>
>> I must add
>> the tab template contains
>>
>> <$tiddler tiddler=<>>
>> <$transclude mode="block" />
>> 
>>
>> and each tab contains 
>> <$list filter={{!!filter}}>
>>
>> 
>>
>> The tabs work stand alone
>>
>> Tones
>>
>> On Wednesday, 21 July 2021 at 23:55:11 UTC+10 TW Tones wrote:
>>
>>> Soren,
>>>
>>> Given this thread, I am not sure if I am on track here, but reading your 
>>> Original post it seems so.
>>>
>>> As I understand it you want to use a filter in a tab tiddler to 
>>> determine if it should have the tab displayed.
>>>
>>> The thing is the tabs macro is not designed for conditional tab display, 
>>> it simply wants a list of tiddlers. If this could all be rammed into a 
>>> single filter then all would be fine. However you not only want to make use 
>>> of another variable or in this case a field but that field contains a 
>>> filter. This is asking too much of the filter syntax.
>>>
>>> What I have done in my solution was to generate the list of tiddlers 
>>> that would be tabs according to you conditions and feed only the result to 
>>> the tabs macro.
>>>
>>>- In my small test not performance issues, and I do not expect their 
>>>to be
>>>- I think what is happening in your case if the reduce etc... is 
>>>adding unnecessary complexity to the performance of the tabs macro.
>>>
>>>
>>> Here is the core logic tested on tiddlywiki.com and pre-release 
>>> incidentally.
>>>
>>> \define tabs-with-content()
>>> <$list filter="[tag[Tag]]" >
>>><$list filter="[all[current]get[filter]]" variable=found-filter>
>>>   <$list 
>>> filter="[subfiltercount[]!match[0]then]">
>>>
>>>
>>>
>>> 
>>> \end
>>>
>>> <$wikify name=tabs-with-content text="<>">
>>> <$macrocall $name=tabs tabsList=<> 
>>> template="tabtemplate"/>
>>> 
>>>
>>> If this does not make sense I will package the tiddlers in this test for 
>>> you.
>>>
>>> The above example may be a good test case if we wanted to invent a 
>>> method to make filters more sophisticated basically permit ones that allow 
>>> you to avoid the nested lists I used, however as stated previously dont be 
>>> shy using nested lists, because each level of nesting allows to generate a 
>>> new variable and keep the old ones in this case found-filter while keeping 
>>> currentTiddler from the first filter.
>>>
>>> My preference would be a shorthand method when presenting variables as a 
>>> parameter, in this case <> such that it is first 
>>> wikified rather than using the ungainly wikify widget and its need to wrap 
>>> the macro call. Eg a a parameter ((tabs-with-content)) or in filters 
>>> (tabs-with-content)
>>> Alternatively TiddlyWiki would detect the need for wikification of that 
>>> variable/macro and do it itself.
>>>
>>>
>>> Regards
>>> tones
>>>
>>>
>>> On Wednesday, 21 July 2021 at 22:15:12 UTC+10 Soren Bjornstad wrote:
>>>
 Saq, the intermittent refresh every 5 seconds updates a clock and 
 Pomodoro timer. The reason it's puzzling is that it doesn't appear by 
 default in the public edition. If you're curious, tick the "clock" 
 checkbox 
 in the FeatureFlags tiddler.

 I'll give the :filter version a try later. I suspect I didn't think to 
 use filter and subfilter toge

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[TW Tones]

Springer,

The text field is using a textarea definition and other field just text. 
You can have what we often call multi-line fields, however if you use the 
built in field editor in the edit template you will break the line feeds.

If that is what you are after consider raising a new thread.

Tones

On Friday, 23 July 2021 at 12:39:23 UTC+10 theok...@gmail.com wrote:

> Soren,
>
> Thanks for responding so fast!
>
> When I have more time I'll have to look for other rendering differences, 
> but the short answer is in hind-sight I now understand how custom CSS could 
> do everything I was seeing. Unfortunately, it didn't occur to me that you'd 
> used custom CSS to alter how the wikitext markup renders. My first instinct 
> was that something was wrong on my end because I was/am the learner. And 
> honestly now I'll go back and look at your stylesheet because I do like it. 
> Maybe a simple warning up front for people to not worry about it.
>
> Yes, your tiddler on "Block Mode and Inline Mode" did help me have an "ah 
> ha!" moment in understanding how TiddlyWiki works. I do try to stick to 
> only using wikitext whenever I can even in tables with the exception of 
> . The simpler I can keep things when things don't work it's less for me 
> to trouble shoot. I discovered the CodeMirror editor plugin for adding line 
> numbers to tiddlers in edit mode and that has help a ton, and I'm using 
> Notepad++ for the same reason when formatting larger blocks of text at once.
>
> But I'm still confused as to what the differences are in how things behave 
> in different places. For example back to my spacing issues general input in 
> a tiddler in edit mode versus in a custom field. From what I've read it 
> makes it seem like they should behave the same but they don't. Again some 
> of the most basic things spaces and carriage returns. In tiddler edit mode 
> spaces are sometimes ignored and carriage returns by default can hide and 
> break things, but if I paste text into a custom field it seems to ignore 
> carriage returns. But they are both supposed to be just text fields so 
> shouldn't they behave the same? It's things like these that make me 
> perpetually think there is something possibly very basic I'm missing or not 
> understanding. 
>
> On Thursday, July 22, 2021 at 8:27:09 PM UTC-4 Soren Bjornstad wrote:
>
>> Also, my comment should definitely say “vertical space,” not “horizontal 
>> space,” haha.
>>
>> On Thursday, July 22, 2021 at 7:26:02 PM UTC-5 Soren Bjornstad wrote:
>>
>>> Paul,
>>>
>>> 1. No matter what I do and what I've searched for has been able to 
 explain why some things render differently for me. This has often caused 
 me 
 to stop and spend large quantities of time trying to figure out what is 
 wrong. For example. In no version of TiddlyWiki (or browser or operating 
 system) that I've downloaded does Heading 2 render with an underline. 
 Doesn't happen. Ever. But it does in Grok TiddlyWiki. 

>>>
>>> Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
>>> some things look different. In $:/sib/Stylesheet, you'll find:
>>>
>>> /* Add more horizontal space and a border for headings, except the 
>>> title. */
>>> h2:not(.tc-title) {
>>>   /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
>>> calculating ex-height differently, so eyeballed an appropriate number of 
>>> inches*/
>>>   margin-top: 0.4in;
>>>   padding-bottom: 5px;
>>>   *border-bottom: 0.05px solid <>;*
>>> }
>>>
>>> Are you able to give some more examples of this? You're not the first 
>>> person who's been confused by the fact that Grok TiddlyWiki doesn't look 
>>> exactly like a stock TiddlyWiki because I've configured it differently. 
>>> Maybe I need to point that out somewhere.
>>>  
>>>
 BTW, an article on where spaces are ignored and where they break things 
 and why would be AMAZING.

>>>
>>> Does block mode and inline mode 
>>>  help 
>>> at all? That's specifically about carriage returns, but those are usually 
>>> more confusing than actual spaces in my experience.
>>>
>>

-- 
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/09ac1982-0a89-45fa-a7c7-51e0bc023063n%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[TW Tones]

Soren,

Can you share the data set, or a dummy one for us to look at performance 
improvements?

I presume you have reviewed you filters in respect of their performance here 
?
Tones

On Friday, 23 July 2021 at 10:17:24 UTC+10 Soren Bjornstad wrote:

> Tones, thanks for putting this together, but your solution is slower than 
> mine as far as I can tell (no easy way to instrument that since it has a 
> very different number of filters, but the difference is apparent from 
> clicking around a bit).
>
> Saq, I can't get your filter to work and I can't see how it would work in 
> theory either now that I look at it – the !!condition in the subfilter is 
> getting the condition field on the tiddler in which the tab list is being 
> rendered, whereas it needs to be the *tab* tiddler that's coming in on 
> the input of the subfilter operator…right? Or am I just being dense? In my 
> :reduce version it has a different meaning because :reduce actually 
> resets the currentTiddler variable to match the input value currently being 
> processed .
>
> With the additional optimization work I did the other night, including 
> optimizing the filters on each tab as Saq pointed out, I would say it's now 
> performing acceptably with my current version, if only barely on a slower 
> computer. So if nobody has any other ideas, I think I can leave it where it 
> is for now.
>
>
> On Wednesday, July 21, 2021 at 8:58:05 AM UTC-5 TW Tones wrote:
>
>> Oops;
>>
>> I must add
>> the tab template contains
>>
>> <$tiddler tiddler=<>>
>> <$transclude mode="block" />
>> 
>>
>> and each tab contains 
>> <$list filter={{!!filter}}>
>>
>> 
>>
>> The tabs work stand alone
>>
>> Tones
>>
>> On Wednesday, 21 July 2021 at 23:55:11 UTC+10 TW Tones wrote:
>>
>>> Soren,
>>>
>>> Given this thread, I am not sure if I am on track here, but reading your 
>>> Original post it seems so.
>>>
>>> As I understand it you want to use a filter in a tab tiddler to 
>>> determine if it should have the tab displayed.
>>>
>>> The thing is the tabs macro is not designed for conditional tab display, 
>>> it simply wants a list of tiddlers. If this could all be rammed into a 
>>> single filter then all would be fine. However you not only want to make use 
>>> of another variable or in this case a field but that field contains a 
>>> filter. This is asking too much of the filter syntax.
>>>
>>> What I have done in my solution was to generate the list of tiddlers 
>>> that would be tabs according to you conditions and feed only the result to 
>>> the tabs macro.
>>>
>>>- In my small test not performance issues, and I do not expect their 
>>>to be
>>>- I think what is happening in your case if the reduce etc... is 
>>>adding unnecessary complexity to the performance of the tabs macro.
>>>
>>>
>>> Here is the core logic tested on tiddlywiki.com and pre-release 
>>> incidentally.
>>>
>>> \define tabs-with-content()
>>> <$list filter="[tag[Tag]]" >
>>><$list filter="[all[current]get[filter]]" variable=found-filter>
>>>   <$list 
>>> filter="[subfiltercount[]!match[0]then]">
>>>
>>>
>>>
>>> 
>>> \end
>>>
>>> <$wikify name=tabs-with-content text="<>">
>>> <$macrocall $name=tabs tabsList=<> 
>>> template="tabtemplate"/>
>>> 
>>>
>>> If this does not make sense I will package the tiddlers in this test for 
>>> you.
>>>
>>> The above example may be a good test case if we wanted to invent a 
>>> method to make filters more sophisticated basically permit ones that allow 
>>> you to avoid the nested lists I used, however as stated previously dont be 
>>> shy using nested lists, because each level of nesting allows to generate a 
>>> new variable and keep the old ones in this case found-filter while keeping 
>>> currentTiddler from the first filter.
>>>
>>> My preference would be a shorthand method when presenting variables as a 
>>> parameter, in this case <> such that it is first 
>>> wikified rather than using the ungainly wikify widget and its need to wrap 
>>> the macro call. Eg a a parameter ((tabs-with-content)) or in filters 
>>> (tabs-with-content)
>>> Alternatively TiddlyWiki would detect the need for wikification of that 
>>> variable/macro and do it itself.
>>>
>>>
>>> Regards
>>> tones
>>>
>>>
>>> On Wednesday, 21 July 2021 at 22:15:12 UTC+10 Soren Bjornstad wrote:
>>>
 Saq, the intermittent refresh every 5 seconds updates a clock and 
 Pomodoro timer. The reason it's puzzling is that it doesn't appear by 
 default in the public edition. If you're curious, tick the "clock" 
 checkbox 
 in the FeatureFlags tiddler.

 I'll give the :filter version a try later. I suspect I didn't think to 
 use filter and subfilter together in one run!

 On Wednesday, July 21, 2021 at 5:57:42 AM UTC-5 saq.i...@gmail.com 
 wrote:

> Hi Soren, glad that was helpful. When I worked on performance 
> improvements for Stre

Re: [tw5] I broke the json pre-release :|

[TW Tones]

Springer,

I totally agree, we need to prepare for any ungainly titles and fieldnames. 
I suppose my point is to not to abuse this and restate the value of keeping 
a limited set of naming rules when developing macros and plugins. Basically 
proposing the use of Okams razor. The rules are meant to be broken but 
giving one self some naming standards will always help. If I write a plugin 
or macro I would not make unnecessary use of the freedom, but I certainly 
will where it is of benefit. Of course for some with different languages 
they have good reason to make use of the new possibilities.

I suppose for me the hard part is sharing this knowledge and experience to 
advise people they may have being given sufficient rope to kill there wiki, 
and to remain circumspect.

Regards
Tones
On Friday, 23 July 2021 at 00:50:25 UTC+10 springer wrote:

> Tones and Mario,
>
> For public-facing projects, being able to name tiddlers with natural 
> language expressions (including spaces) has been essential, and it seems 
> much of the expanded power of fields in 5.2.0 will come from scanning for 
> matches between field names and tiddler titles. 
>
> (Emojis and such may seem trivial, but certain specialized unicode 
> characters like Σ, plus expressions in two-byte languages like 字, are 
> surely going to be leveraged by a significant user base as well.)
>
> So, as much as it may seem logical to stick to CamelCase titles and 
> a-z_special.string fieldnames for certain users, it seems the 
> flexible-field-names horse is going to be galloping out of the barn as soon 
> as the new version is available.
>
> Might we figure out some way to test the compatibility of existing plugins 
> (such as Shiraz) more systematically than by trial and error?
>
> -Springer
>
> On Thursday, July 22, 2021 at 12:24:46 AM UTC-4 TW Tones wrote:
>
>> Mario,
>>
>> I am glad someone concurs. For me with my de facto standards and the new 
>> freedom, if a field name looks like a tiddler title it possibly is.
>>
>> Do you think many ancient and / or unsupported plugins will break?,. if 
>> they use fields even extensively the issue will only be if they are used 
>> against new fieldname standards. And until now at least we tended to honour 
>> any values if not fieldnames.
>>
>> I will be honest though few if any system tiddlers I create have spaces 
>> or quotes of any kind. even tags are usually single text strings, and I do 
>> think I will stick to this, as it simplifies code. but yes, use it when the 
>> exception makes sense.
>>
>> I have not yet considered what we may achieve by having field names that 
>> can be wikified into something else, but again I personally intend to 
>> proceed with caution. Perhaps the documentation can give some advice to 
>> this effect, for example currently the fieldname restrictions help us when 
>> generating csv files and if field names (and values) contain spaces, or 
>> commas and quotes this may no longer be true. The documentation should 
>> continue to list the previous limited naming standards as well. 
>>
>> I must say I also have de facto naming standards for titles even although 
>> they are quite flexible, in fact most that I code follow a simple and 
>> limited range. I like to leave the flexibility for when its needed. The one 
>> exception is when a title is also textual content like a sentence or 
>> paragraph.
>>
>> Regards
>> Tones
>> On Thursday, 22 July 2021 at 13:56:18 UTC+10 PMario wrote:
>>
>>> On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:
>>>  
>>>
 However am I the only one who still intends to keep field names to a 
 defacto naming standard such as i-am-afield no caps or spaces? so It is 
 easy for me to tell field names apart from text and titles!

>>>
>>> No -- you are not.
>>>  
>>>
 Of course I look forward to naming fields using tiddler titles (and the 
 value a relationship type etc..). and to contain special prefixes or 
 suffixes such as "-link" or (link)  but as a rule I would like a little 
 structure and naming rules. 

>>>
>>> You wrote, you want to have tiddler titles as field names. So your 
>>> field-rules have to be the same or a superset of your title rules. I would 
>>> be surprised, if "no caps or spaces" is one of them. 
>>>  
>>>
 This always helps retain a degree of simplicity when managing lots of 
 complexity.

>>>
>>> Oh it will be funny, to deal with all the support requests here in the 
>>> group, because some ancient and / or unsupported plugins will break. ... 
>>> I'm not even sure, what my own plugins will do with "spaces" in field 
>>> names. ...  I will have to check that. 
>>>
>>> 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://group

[tw5] Re: What other tools compliment TiddlyWiki well? [discussion]

[Jason Houle]

I just worked on a tool for syncing my Keep notes to TW today, it is a JS 
bookmarklet that loads and executes this gist 
. I 
have only tested this on Chrome so far and there are still a couple kinks 
to work out, but I'm happy with it so far.

1. Highlight this text and drag it into your bookmarks bar:

javascript:var 
id%3D"0937d5af819d1914c7803f22ee8752d6"%2Cfile%3D"bookmarklet-export-keep.js"%2Cuser%3D"jasonmhoule"%2Cxhr%3Dnew
 
XMLHttpRequest%3Bxhr.overrideMimeType("application%2Fjson")%3Bxhr.open("GET"%2C"https%3A%2F%2Fgist.githubusercontent.com%2F"%2Buser%2B"%2F"%2Bid%2B"%2Fraw%2F"%2Bfile%2B"%3F"%2BMath.random())%3Bxhr.onreadystatechange%3Dfunction()%7Bif(4%3D%3D%3Dxhr.readyState)if(200%3D%3D%3Dxhr.status)console.log("Successfully
 
loaded 
gist%3A"%2C%7Bid%3Aid%2Cfile%3Afile%2Cuser%3Auser%2Cresponse%3Axhr.responseText%7D)%2C(0%2Ceval)(xhr.responseText)%3Belse%7Bvar
 
a%3D"GitHub Gist file did not load successfully and instead returned a 
status code of 
"%2Bxhr.status%2B"."%3Bconsole.error(a%2C%7Bid%3Aid%2Cfile%3Afile%2Cuser%3Auser%7D)%3Balert(a)%7D%7D%3Bxhr.send(null)%3Bvoid+0

2. Navigate to Keep. The code will iterate through all the tiddlers that 
are loaded to the view, so if your Keep is anywhere near as cluttered as 
mine, I suggest trying this on a subset. For example, I tag certain notes 
as #export, and then I can open that tag in the Keep web navbar to execute 
this script just on them.

3. Once you have the 'target' tiddlers in view, click on the bookmarklet 
and watch it pop each tiddler open in turn (one per second). Once it is 
done with this, it will download a keep-notes.json file. You can drag this 
single file into your wiki and it will import one tiddler per note. Note 
that I also use (an early version of) Projectify so the code tags each 
tiddler with "Inbox" and "todo" so that it lands for processing in TW. I 
have not looked into pulling the other Keep tags into the tiddler but will 
probably do that.

The code currently does not archive tiddlers automatically - I may add that 
some day, but want to kick the tires quite a bit more first. Also note that 
because the bookmarklet loads the gist from GH, if I make any changes in 
the future, it is the changed code that will be triggered. (I'm not sure if 
I can pin the bookmarklet down to a single commit, that would probably be 
useful!)

Anyway, thought I would offer this up to see if there are thoughts/feedback 
for improvement.
On Thursday, July 22, 2021 at 3:27:21 PM UTC-5 Si wrote:

> Thanks for the responses.
>
> I like Keep, very nice level of simplicity and pleasant to use. Personally 
> I try to avoid Google stuff where I can, but I did notice this very nice 
> keep-style Android app that has recently appeared on Fdroid: 
> https://github.com/msoultanidis/quillnote. Unfortunately it's Android 
> only, but I'll be keeping an eye on it in case they add a way to sync the 
> notes to a computer as markdown files.
>
> @Tones 
>
> > I don't concur with your statement Si, as I think I said before  *In my 
> opinion a major weakness of TiddlyWiki is that it is not well suited to 
> quickly capturing information on the fly with minimal friction.*
>
> I wouldn't want to spend much time defending my view, as I think what 
> does/doesn't count as friction is pretty subjective. My biggest problems 
> are on mobile, where saving a single file wiki with Tiddloid takes too long 
> for me to ever really feel like using it. I had forgotten about 
> Projectify's quick-add feature though, which I agree is very useful for 
> quick-capture.
>
> > I did look into getting tiddlywiki into a browser side bar in the past. 
> I believed it worked in FireFox, but if not universal it is less 
> interesting. 
>
> There are a few Firefox extensions for doing this, but I couldn't get any 
> to work with a local file. Perhaps they will work with the node.js version. 
> Vivaldi has a built in feature for doing this which works very nicely with 
> TiddlyWiki: https://help.vivaldi.com/desktop/panels/web-panels/
> On Thursday, 22 July 2021 at 05:35:35 UTC+1 TW Tones wrote:
>
>> Keep is popular.
>>
>> I did look into getting tiddlywiki into a browser side bar in the past. I 
>> believed it worked in FireFox, but if not universal it is less interesting. 
>> That is the advantage of keep if you use a few of googles tools.
>>
>> Tones
>>
>> On Thursday, 22 July 2021 at 13:34:37 UTC+10 cj.v...@gmail.com wrote:
>>
>>> I'm thinking it largely depends on the "ecosystem" one may be living in.
>>>
>>> Seeing as I've sold my soul to Google, Google Keep is my goto quick note 
>>> taker.
>>>
>>> I can access the full screen Google Keep, sidebar Google Keep when I'm 
>>> in the other Google Apps, and have the Google Keep Chrome Extension, to 
>>> quickly take notes while viewing some web page.
>>>
>>> So quick note taking for some heavy-duty note making in TiddlyWiki later.
>>>
>>> Mind you, I only ev

[tw5] Re: Announcing Editor-Autolist-Markdown

[Daryl Sun]

Hello!

Thank you very much for this plugin. I use Markdown for note-taking, and 
it's always driven me crazy that I have to manually set indentation for my 
bullet-lists, since I can't use Editor-Autolist. So I'm very pleased to see 
that a Markdown version now exists.

However, I've found a bug where the plugin stops working if the editor 
toolbar is hidden. I discovered this because I use Big Text Area from 
Stroll, and I couldn't get Editor-Autolist-Markdown to work. I managed to 
replicate the bug in an empty TiddlyWiki file with only the official 
Markdown plugin +  Editor-Autolist-Markdown, and everything else default, 
*but* the editor toolbar is disabled. I tested this in Firefox on Windows 
10.

I understand if this is a very unusual use case and it's not a high 
priority to fix it. I have a knack for finding strange bugs.
On Friday, July 16, 2021 at 1:13:15 AM UTC+8 jason...@gmail.com wrote:

> Hi all, I have been learning about TW5 and making increasing use of it 
> over the past ~9 months. It is an incredible tool with a great ecosystem of 
> support, so as I begin to make some customizations I wanted to share these 
> back for the community.
>
> I have put together a plugin based on Saq's excellent editor-autolist. I 
> primarily use markdown for my notes so I have adapted it for markdown lists.
>
> I have used bullet lists pretty extensively in the MS ecosystem in my 
> work, so in addition to the list indent and continuation, I added features 
> to indent/unindent multiple lines, and to move list sections up or down.
>
> Please check out the GH repo 
>  and the hosted 
> plugin . This is 
> the initial release so I welcome your feedback and suggestions for 
> improvement!
>

-- 
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/26ca30bf-9807-40e5-a1ec-d6bfce5ea972n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

['Mark S.' via TiddlyWiki]

At the moment, I just want to know what you mean by search steps, since I 
don't see that specifically documented.

My overall thought about searches was that we need to see the text of 
tiddlers, or maybe the first 100 characters of text, rather than the titles 
since the titles are nearly meaningless.

Thanks!

On Thursday, July 22, 2021 at 7:29:25 PM UTC-7 fred@gmail.com wrote:

> @walt released 0.0.3-beta https://fastfreddy.gitlab.io/streams-fusion/   not 
> thoroughly tested, be very careful and clone/backup extensively
>
>
> @mark s : yes, my setup is heavily customized; not a good solution for you 
> if you're not super comfortable tinkering; boils down to installing the 
> command palette and tweaking the search steps. The shortcut key handling 
> makes it interesting. What specifically are you looking to do?
>
> On Thu, 22 Jul 2021 at 19:47, 'Mark S.' via TiddlyWiki <
> tiddl...@googlegroups.com> wrote:
>
>> Can you explain search steps? How they're activated, etc. It looks like 
>> they have been very customized for your setup.
>>
>> Thanks!
>>
>> On Thursday, July 22, 2021 at 3:06:42 PM UTC-7 fred@gmail.com wrote:
>>
>>> @Mark S; I particularly like the command palette 
>>>  plugin for searches.
>>>
>>> Please note it is not designed for Streams, but can be made to work 
>>> quite nicely with it because the search steps are highly configurable 
>>> through the  $:/plugins/souk21/commandpalette/CommandPaletteSearchSteps 
>>> tiddler. Here's an example of what I use at work; you'll notice I give 
>>> precedence to title matches (they'll be at the top of the results) and use 
>>> the get-streams-root[] filter extensively. The command palette adds a 
>>> category (hint) in the search results which I find helpful.
>>>
>>> {
>>> "steps": [
>>>   {"filter": 
>>> "[!is[system]tag[todo]search:title:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>>>  "hint": "todo (titles)", "caret": "42"},
>>>   {"filter": 
>>> "[!is[system]tag[todo]search:text:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>>>  "hint": "todo (text)", "caret": "41"},
>>>   {"filter": 
>>> "[!is[system]tag[Meeting]search:title:literal[]!sort[title]]", "hint": 
>>> "meetings (main)", "caret": "45"},
>>>   {"filter": 
>>> "[!is[system]tag[Journal]search:title:literal[]!sort[title]first[2]]", 
>>> "hint": "meetings (titles)", "caret": "45"},
>>>   {"filter": 
>>> "[!is[system]tag[Journal]search:text:literal[]get-stream-root[]!sort[title]]",
>>>  "hint": "meetings (text)", "caret": "44"},
>>>   {"filter": 
>>> "[!is[system]search:title:literal[]get-stream-root[]]", "hint": "others 
>>> (titles)", "caret": "33"},
>>>   {"filter": "[!is[system]search:text:literal[]get-stream-root[]]", 
>>> "hint": "others (text)", "caret": "32"},
>>>   {"filter": 
>>> "[!is[system]tag[todo]search:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]tag[done]]",
>>>  "hint": "completed", "caret": "42"},
>>>   {"filter": "[!is[system]search::literal[]get-stream-root[]]", 
>>> "hint": "all", "caret": "28"}
>>> ]
>>> }
>>>
>>> I have configured the command palette to fire on a single key shortcut (
>>> /). Whilst TiddlyWiki offers keyboard shortcuts, they fire everywhere 
>>> out of the box, even within text boxes (not ideal for single key 
>>> shortcuts!), so my setup relies on the mousetrap 
>>>  
>>> plugin: hitting / in a text box does not fire the command palette. I am 
>>> working on a tweak that will have a richer set of search steps 
>>> configuration, so that I can invoke the command palette to search for tasks 
>>> (I use projectify ) using shift+/ and to 
>>> search in other tiddlers when I hit /.
>>>
>>> In other parts of the UI, I have essentially inserted the subfilter "
>>> get-stream-root[]" everywhere, so that the recent tab, the sidebar 
>>> searches, etc only show root tiddlers in the results. 
>>>
>>> I think one of the other members in the community here configured the 
>>> names of node tiddlers to be prefixed with $:/ which makes them system 
>>> tiddlers, which effectively hides them from most searches... another option 
>>> worth considering and simpler to setup.
>>>
>>> On Thu, 22 Jul 2021 at 15:02, Saq Imtiaz  wrote:
>>>

 Is there a search tool or plugin that works with streams? Streams is 
> neat to take notes with, but searching is problematic since the default 
> search shows you only the titles. Possibly someone has already written a 
> custom search? 
>

 @Mark S:

 I don't think there is a good generalized solution for this yet. Needs 
 vary depending on people's workflow and title naming setup within Streams. 
 I have posted a search customization for a specific users workflow at one 
 point to show what customizati

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Paul Hampshire]

Soren,

Thanks for responding so fast!

When I have more time I'll have to look for other rendering differences, 
but the short answer is in hind-sight I now understand how custom CSS could 
do everything I was seeing. Unfortunately, it didn't occur to me that you'd 
used custom CSS to alter how the wikitext markup renders. My first instinct 
was that something was wrong on my end because I was/am the learner. And 
honestly now I'll go back and look at your stylesheet because I do like it. 
Maybe a simple warning up front for people to not worry about it.

Yes, your tiddler on "Block Mode and Inline Mode" did help me have an "ah 
ha!" moment in understanding how TiddlyWiki works. I do try to stick to 
only using wikitext whenever I can even in tables with the exception of 
. The simpler I can keep things when things don't work it's less for me 
to trouble shoot. I discovered the CodeMirror editor plugin for adding line 
numbers to tiddlers in edit mode and that has help a ton, and I'm using 
Notepad++ for the same reason when formatting larger blocks of text at once.

But I'm still confused as to what the differences are in how things behave 
in different places. For example back to my spacing issues general input in 
a tiddler in edit mode versus in a custom field. From what I've read it 
makes it seem like they should behave the same but they don't. Again some 
of the most basic things spaces and carriage returns. In tiddler edit mode 
spaces are sometimes ignored and carriage returns by default can hide and 
break things, but if I paste text into a custom field it seems to ignore 
carriage returns. But they are both supposed to be just text fields so 
shouldn't they behave the same? It's things like these that make me 
perpetually think there is something possibly very basic I'm missing or not 
understanding. 

On Thursday, July 22, 2021 at 8:27:09 PM UTC-4 Soren Bjornstad wrote:

> Also, my comment should definitely say “vertical space,” not “horizontal 
> space,” haha.
>
> On Thursday, July 22, 2021 at 7:26:02 PM UTC-5 Soren Bjornstad wrote:
>
>> Paul,
>>
>> 1. No matter what I do and what I've searched for has been able to 
>>> explain why some things render differently for me. This has often caused me 
>>> to stop and spend large quantities of time trying to figure out what is 
>>> wrong. For example. In no version of TiddlyWiki (or browser or operating 
>>> system) that I've downloaded does Heading 2 render with an underline. 
>>> Doesn't happen. Ever. But it does in Grok TiddlyWiki. 
>>>
>>
>> Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
>> some things look different. In $:/sib/Stylesheet, you'll find:
>>
>> /* Add more horizontal space and a border for headings, except the title. 
>> */
>> h2:not(.tc-title) {
>>   /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
>> calculating ex-height differently, so eyeballed an appropriate number of 
>> inches*/
>>   margin-top: 0.4in;
>>   padding-bottom: 5px;
>>   *border-bottom: 0.05px solid <>;*
>> }
>>
>> Are you able to give some more examples of this? You're not the first 
>> person who's been confused by the fact that Grok TiddlyWiki doesn't look 
>> exactly like a stock TiddlyWiki because I've configured it differently. 
>> Maybe I need to point that out somewhere.
>>  
>>
>>> BTW, an article on where spaces are ignored and where they break things 
>>> and why would be AMAZING.
>>>
>>
>> Does block mode and inline mode 
>>  help 
>> at all? That's specifically about carriage returns, but those are usually 
>> more confusing than actual spaces in my experience.
>>
>

-- 
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/99be54fd-fa77-4701-9faf-c08c751ad8c3n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@walt released 0.0.3-beta https://fastfreddy.gitlab.io/streams-fusion/   not
thoroughly tested, be very careful and clone/backup extensively


@mark s : yes, my setup is heavily customized; not a good solution for you
if you're not super comfortable tinkering; boils down to installing the
command palette and tweaking the search steps. The shortcut key handling
makes it interesting. What specifically are you looking to do?

On Thu, 22 Jul 2021 at 19:47, 'Mark S.' via TiddlyWiki <
tiddlywiki@googlegroups.com> wrote:

> Can you explain search steps? How they're activated, etc. It looks like
> they have been very customized for your setup.
>
> Thanks!
>
> On Thursday, July 22, 2021 at 3:06:42 PM UTC-7 fred@gmail.com wrote:
>
>> @Mark S; I particularly like the command palette
>>  plugin for searches.
>>
>> Please note it is not designed for Streams, but can be made to work quite
>> nicely with it because the search steps are highly configurable through
>> the  $:/plugins/souk21/commandpalette/CommandPaletteSearchSteps tiddler.
>> Here's an example of what I use at work; you'll notice I give precedence to
>> title matches (they'll be at the top of the results) and use the
>> get-streams-root[] filter extensively. The command palette adds a
>> category (hint) in the search results which I find helpful.
>>
>> {
>> "steps": [
>>   {"filter": 
>> "[!is[system]tag[todo]search:title:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>>  "hint": "todo (titles)", "caret": "42"},
>>   {"filter": 
>> "[!is[system]tag[todo]search:text:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>>  "hint": "todo (text)", "caret": "41"},
>>   {"filter": 
>> "[!is[system]tag[Meeting]search:title:literal[]!sort[title]]", "hint": 
>> "meetings (main)", "caret": "45"},
>>   {"filter": 
>> "[!is[system]tag[Journal]search:title:literal[]!sort[title]first[2]]", 
>> "hint": "meetings (titles)", "caret": "45"},
>>   {"filter": 
>> "[!is[system]tag[Journal]search:text:literal[]get-stream-root[]!sort[title]]",
>>  "hint": "meetings (text)", "caret": "44"},
>>   {"filter": "[!is[system]search:title:literal[]get-stream-root[]]", 
>> "hint": "others (titles)", "caret": "33"},
>>   {"filter": "[!is[system]search:text:literal[]get-stream-root[]]", 
>> "hint": "others (text)", "caret": "32"},
>>   {"filter": 
>> "[!is[system]tag[todo]search:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]tag[done]]",
>>  "hint": "completed", "caret": "42"},
>>   {"filter": "[!is[system]search::literal[]get-stream-root[]]", 
>> "hint": "all", "caret": "28"}
>> ]
>> }
>>
>> I have configured the command palette to fire on a single key shortcut (/).
>> Whilst TiddlyWiki offers keyboard shortcuts, they fire everywhere out of
>> the box, even within text boxes (not ideal for single key shortcuts!), so
>> my setup relies on the mousetrap
>> 
>> plugin: hitting / in a text box does not fire the command palette. I am
>> working on a tweak that will have a richer set of search steps
>> configuration, so that I can invoke the command palette to search for tasks
>> (I use projectify ) using shift+/ and to
>> search in other tiddlers when I hit /.
>>
>> In other parts of the UI, I have essentially inserted the subfilter "
>> get-stream-root[]" everywhere, so that the recent tab, the sidebar
>> searches, etc only show root tiddlers in the results.
>>
>> I think one of the other members in the community here configured the
>> names of node tiddlers to be prefixed with $:/ which makes them system
>> tiddlers, which effectively hides them from most searches... another option
>> worth considering and simpler to setup.
>>
>> On Thu, 22 Jul 2021 at 15:02, Saq Imtiaz  wrote:
>>
>>>
>>> Is there a search tool or plugin that works with streams? Streams is
 neat to take notes with, but searching is problematic since the default
 search shows you only the titles. Possibly someone has already written a
 custom search?

>>>
>>> @Mark S:
>>>
>>> I don't think there is a good generalized solution for this yet. Needs
>>> vary depending on people's workflow and title naming setup within Streams.
>>> I have posted a search customization for a specific users workflow at one
>>> point to show what customizations for search might look like.
>>>
>>> If you just want search results to show the root tiddler title as
>>> opposed to the titles of individual nodes, the attached file adds a tab to
>>> the search results to do that. If I remember correctly, title matches are
>>> returned unchanged whereas text matches only return the root tiddler.
>>>
>>> The missing piece is of course that once you find and open the root
>>> tiddler, it can be tricky finding the text you searched for within that
>>> stream.
>>>
>>> --
>>>
>> You rece

[tw5] Re: Getting relink to prevent obsolete permalinks

[Charlie Veniot]

Just a reminder that, although maybe a little odd-looking, all kinds of 
neat filtering can be setup in a tiddler link (i.e. for tiddler lookup from 
outside a TiddlyWiki) to help prevent link rot.

For example:
https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:
*[uid[2]]*%20*[match[UID-Permalink%20Project]]* 


The reason for that kind of link is to try to make sure that the link, 
posted in some forum, and/or put in a blog, and/or you-name-it, has the 
best chance of standing the test of time.

The beauty of that kind of link is that, me having this habit of 
continuously tweaking my tiddler titles, the link to the tiddler should 
always work as long as I never muck with the uid field (that would have to 
be a pretty bad accident.)

The best of all worlds in a way.   A stable link via the UID, and a decent 
description via tiddler title, even if the title wound up changing.

If we wanted to handle link rot, we could:
https://tiddlywiki-programming.neocities.org/CJ_TiddlyWikiProgramming.html#:
[uid[*3*]]%20[match[UID-dPermalink%20Project]]%20*+[else[error404?]]* 


Yeah, verbose URL's, but when one wants to minimize the risk of link rot 
and/or handle link rot ...

So anybody can share a link to a tiddler with whatever kind of filtering in 
the URL that makes the best sense for him/her and how his/her TiddlyWiki is 
organized.
On Thursday, July 22, 2021 at 12:14:00 PM UTC-3 springer wrote:

> Tones,
>
> This again is a place where different users may have different needs. I 
> love the fact that if I share a permalink, the #TiddlerTitle at the end is 
> not an indecipherable UID, but something recognizable and meaningful to the 
> recipient (and even to myself, going back into my emails and recognizing 
> what I shared). 
>
> And as much as you may "choose my tiddler names well enough when needed so 
> they need not change in future",  renaming a tiddler is not always a matter 
> of realizing that you failed to have foresight the first time around. (My 
> reason for invoking the Bombay to Mumbai change -- or Bruce to Caitlin if 
> you prefer -- is that the world *about* which we take and share notes does 
> not always cater to our desire for stability. ;)
>
> I do realize that even without changing relink, we could mitigate obsolete 
> permalinks (when we are aware of them) by setting up a ViewTemplate that 
> works with a "formerly" field (or maybe just with a alias and aliases 
> field), to transclude or redirect when the old permalink lands on an 
> obsolete tiddler. 
>
> -Springer
> On Wednesday, July 21, 2021 at 9:17:10 PM UTC-4 TW Tones wrote:
>
>> Springer et al,
>>
>> Forgive me for repeating myself, although a lot of interesting ideas, I 
>> believe these to be *non-problems.* 
>>
>> A simple solution is available here. an Example would be an alternate 
>> button to simple permalinks, I think someone else used a share icon. When 
>> clicking this on a given tiddler, it would assign a next number to a field 
>> in the tiddler (basically issuing a unique value field - not a UID or 
>> serial or GUID) then use this field/number to uniquely identify the tiddler 
>> shared, so it does not matter if it's title is renamed. Then generate a url 
>> that instead searches for any (but only one) tiddler with that field value.
>>
>> If *anyone asks* I will build this share button soon.
>>
>> That is if someone wants to publish a robust permalink for a tiddler 
>> who's title may change they use a built for purpose alternative to 
>> permalinks. Perhaps the existing name permalinks is misleading, perhaps 
>> they should be impermalinks.
>>
>> Here is a working example
>> a tiddler with the "permalink" field=1
>> the url wiki-url.html#:[permalink[1]] 
>> In the wiki Open target this 
>> can be dragged to bookmarks/favourites
>>
>> However I personally choose my tiddler names well enough when needed so 
>> they need not change in future, and if I am publishing a link somewhere it 
>> is to access specific content. the link has a purpose, and once someone has 
>> the link the purpose is fixed in time and should always honour its original 
>> share.
>>
>> A version of the above method where the link filter 
>> is [has[permalink]last[]] will always link to the largest permalink value, 
>> so one is sharing a link to the latest permalink tiddler or post.
>>
>> Another supportive trick is to hide the field from the editor with a 
>> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
>> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
>> thus once set you have to go out of your way to alter the permalink 
>> value, that is its more permanent.
>>
>> Further developments (optional reading)
>

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Soren Bjornstad]

Also, my comment should definitely say “vertical space,” not “horizontal 
space,” haha.

On Thursday, July 22, 2021 at 7:26:02 PM UTC-5 Soren Bjornstad wrote:

> Paul,
>
> 1. No matter what I do and what I've searched for has been able to explain 
>> why some things render differently for me. This has often caused me to stop 
>> and spend large quantities of time trying to figure out what is wrong. For 
>> example. In no version of TiddlyWiki (or browser or operating system) that 
>> I've downloaded does Heading 2 render with an underline. Doesn't happen. 
>> Ever. But it does in Grok TiddlyWiki. 
>>
>
> Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
> some things look different. In $:/sib/Stylesheet, you'll find:
>
> /* Add more horizontal space and a border for headings, except the title. 
> */
> h2:not(.tc-title) {
>   /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
> calculating ex-height differently, so eyeballed an appropriate number of 
> inches*/
>   margin-top: 0.4in;
>   padding-bottom: 5px;
>   *border-bottom: 0.05px solid <>;*
> }
>
> Are you able to give some more examples of this? You're not the first 
> person who's been confused by the fact that Grok TiddlyWiki doesn't look 
> exactly like a stock TiddlyWiki because I've configured it differently. 
> Maybe I need to point that out somewhere.
>  
>
>> BTW, an article on where spaces are ignored and where they break things 
>> and why would be AMAZING.
>>
>
> Does block mode and inline mode 
>  help 
> at all? That's specifically about carriage returns, but those are usually 
> more confusing than actual spaces in my experience.
>

-- 
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/aaf42348-d1c1-49b9-beee-b60390c8bf2bn%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Soren Bjornstad]

Paul,

1. No matter what I do and what I've searched for has been able to explain 
> why some things render differently for me. This has often caused me to stop 
> and spend large quantities of time trying to figure out what is wrong. For 
> example. In no version of TiddlyWiki (or browser or operating system) that 
> I've downloaded does Heading 2 render with an underline. Doesn't happen. 
> Ever. But it does in Grok TiddlyWiki. 
>

Ah! This is just because Grok TiddlyWiki has custom CSS rules that make 
some things look different. In $:/sib/Stylesheet, you'll find:

/* Add more horizontal space and a border for headings, except the title. */
h2:not(.tc-title) {
  /*margin-top: 6ex; -- for some bizarre reason Firefox and Chrome are 
calculating ex-height differently, so eyeballed an appropriate number of 
inches*/
  margin-top: 0.4in;
  padding-bottom: 5px;
  *border-bottom: 0.05px solid <>;*
}

Are you able to give some more examples of this? You're not the first 
person who's been confused by the fact that Grok TiddlyWiki doesn't look 
exactly like a stock TiddlyWiki because I've configured it differently. 
Maybe I need to point that out somewhere.
 

> BTW, an article on where spaces are ignored and where they break things 
> and why would be AMAZING.
>

Does block mode and inline mode 
 help 
at all? That's specifically about carriage returns, but those are usually 
more confusing than actual spaces in my experience.

-- 
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/d3b0f9f9-431a-46bb-8da0-fd303bd19fdcn%40googlegroups.com.

[tw5] Re: Building a list of tabs dynamically in a performant manner

[Soren Bjornstad]

Tones, thanks for putting this together, but your solution is slower than 
mine as far as I can tell (no easy way to instrument that since it has a 
very different number of filters, but the difference is apparent from 
clicking around a bit).

Saq, I can't get your filter to work and I can't see how it would work in 
theory either now that I look at it – the !!condition in the subfilter is 
getting the condition field on the tiddler in which the tab list is being 
rendered, whereas it needs to be the *tab* tiddler that's coming in on the 
input of the subfilter operator…right? Or am I just being dense? In my 
:reduce version it has a different meaning because :reduce actually resets 
the currentTiddler variable to match the input value currently being 
processed .

With the additional optimization work I did the other night, including 
optimizing the filters on each tab as Saq pointed out, I would say it's now 
performing acceptably with my current version, if only barely on a slower 
computer. So if nobody has any other ideas, I think I can leave it where it 
is for now.


-- 
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/d31f9d76-26f9-4c63-8e12-167e42ae11a9n%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[Paul Hampshire]

Soren,

Thank you for building Grok TiddlyWiki. I'm what I would call a long term 
novice in that I've used TiddlyWiki for a while but only in the past few 
months have I learned what it can truly do. That is in large part to this 
group and Grok TiddlyWiki.  I don't have a programming background and only 
have limited html experience so many of the explanations have been hugely 
helpful. I have found I have had two reoccurring hurdles that make my 
learning slower.

1. No matter what I do and what I've searched for has been able to explain 
why some things render differently for me. This has often caused me to stop 
and spend large quantities of time trying to figure out what is wrong. For 
example. In no version of TiddlyWiki (or browser or operating system) that 
I've downloaded does Heading 2 render with an underline. Doesn't happen. 
Ever. But it does in Grok TiddlyWiki. Another example that took me a ton of 
time to figure out was I had hidden carriage returns mucking things up. 
This happened because I was copy and pasting back and forth between 
programs. No where in any of my reading have I come across an article 
called "Top 10 dumb things you don't know to look for that will screw up 
what you're trying to do". BTW, an article on where spaces are ignored and 
where they break things and why would be AMAZING.

2. As a person new to this stuff, while I'm eternally grateful for what you 
and this community continues to do to help others understand, what might be 
another way to reach the non-programmers is a guide or introduction on how 
to read the documentation, a short and simple "idiots guide" so to speak. 
To use another expression it would be another way to "teach us to fish". I 
completely get that's exactly what you are trying to do with Grok 
TiddlyWiki and it has helped me immensely. BUT every time I go into the 
documentation my eyes cross. I know the answers are there but I don't know 
all the right words to look for to figure things out or how to read what's 
there. Again, Grok TiddlyWiki has helped me a lot, and everyone here is 
great about answering questions, but I know I can't be alone in that I hate 
the idea of asking a question when there is the documentation and Grok 
TiddlyWiki and I still can't figure something out. I'm in the stuff for a 
couple hours with a feeling similar to a word being on the tip your tongue 
but you can't figure it out. Hours of reading thinking I must be missing 
something simple it's got to be in here somewhere. I am 100% confident you 
and some of the others here could do a how-to for reading the documentation 
in a page or two, but it's that bridging the language gap that I'm certain 
is slowing many of us down. 

v/r,

Paul

On Thursday, July 22, 2021 at 12:18:51 PM UTC-4 springer wrote:

> Soren,
>
> I think I'm part of the target audience for Grok TiddlyWiki, despite being 
> a long-time user. I have never given myself a systematic approach, and have 
> instead always learned whatever bits I need to solve this or that 
> problem-at-hand. I'm grateful for your learning tool, and am slowly working 
> through it (systematically including nearly all exercises through Chapter 
> Four, with skimming and selective reading past that, as I've had less time 
> to devote recently). 
>
> The organization seems helpful to me, though like many dabblers I have 
> depth in some areas you call "advanced" and deficits in some basics. A few 
> early portions feel too elementary for me, but I've worked through them 
> anyway, partly to make sure I absorb technical terminology better (where I 
> know how to do X but not what the ingredients are called), and partly 
> because I am frequently surprised, even in early chapters, by what Tones 
> calls the occasional "easter egg" of discovering a new thing.
>
> I did have one frustrating rabbit-hole experience with the RubberDucking 
> exercise, but it was anomalous (I was working on a clone of your book, 
> which contained an error you have since fixed. On my version, you hadn't 
> yet compensated for how you tucked various components into shadows. I 
> "fixed" the exercise filter's punctuation correctly, but it still showed 
> nothing. My Rubber Duck was not at all helpful until it suggested that I 
> dial up the book at your url, where "Eureka!" the actual exercise prompt 
> was different. I could email you the details, but it's not of general 
> interest.)
>
> I'm pretty sure my skills are improving, especially if I think half of a 
> skill is having the right *concepts* for one's skills, and a cogent 
> understanding of their scope and limits.
>
> One thing I specifically appreciate is that a search for "boolean" on your 
> book brought me to a helpful discussion. I had tried in vain to find 
> "boolean" on tiddlywiki.com (where it appears only incidentally around 
> "then" and else") and on https://tobibeer.github.io/tw/filters/  ... (Not 
> getting any helpful hits at these two spots did make me feel pretty crazy!

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

['Mark S.' via TiddlyWiki]

Can you explain search steps? How they're activated, etc. It looks like 
they have been very customized for your setup.

Thanks!

On Thursday, July 22, 2021 at 3:06:42 PM UTC-7 fred@gmail.com wrote:

> @Mark S; I particularly like the command palette 
>  plugin for searches.
>
> Please note it is not designed for Streams, but can be made to work quite 
> nicely with it because the search steps are highly configurable through 
> the  $:/plugins/souk21/commandpalette/CommandPaletteSearchSteps tiddler. 
> Here's an example of what I use at work; you'll notice I give precedence to 
> title matches (they'll be at the top of the results) and use the 
> get-streams-root[] filter extensively. The command palette adds a 
> category (hint) in the search results which I find helpful.
>
> {
> "steps": [
>   {"filter": 
> "[!is[system]tag[todo]search:title:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>  "hint": "todo (titles)", "caret": "42"},
>   {"filter": 
> "[!is[system]tag[todo]search:text:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
>  "hint": "todo (text)", "caret": "41"},
>   {"filter": 
> "[!is[system]tag[Meeting]search:title:literal[]!sort[title]]", "hint": 
> "meetings (main)", "caret": "45"},
>   {"filter": 
> "[!is[system]tag[Journal]search:title:literal[]!sort[title]first[2]]", 
> "hint": "meetings (titles)", "caret": "45"},
>   {"filter": 
> "[!is[system]tag[Journal]search:text:literal[]get-stream-root[]!sort[title]]",
>  "hint": "meetings (text)", "caret": "44"},
>   {"filter": "[!is[system]search:title:literal[]get-stream-root[]]", 
> "hint": "others (titles)", "caret": "33"},
>   {"filter": "[!is[system]search:text:literal[]get-stream-root[]]", 
> "hint": "others (text)", "caret": "32"},
>   {"filter": 
> "[!is[system]tag[todo]search:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]tag[done]]",
>  "hint": "completed", "caret": "42"},
>   {"filter": "[!is[system]search::literal[]get-stream-root[]]", 
> "hint": "all", "caret": "28"}
> ]
> }
>
> I have configured the command palette to fire on a single key shortcut (/). 
> Whilst TiddlyWiki offers keyboard shortcuts, they fire everywhere out of 
> the box, even within text boxes (not ideal for single key shortcuts!), so 
> my setup relies on the mousetrap 
>  
> plugin: hitting / in a text box does not fire the command palette. I am 
> working on a tweak that will have a richer set of search steps 
> configuration, so that I can invoke the command palette to search for tasks 
> (I use projectify ) using shift+/ and to search 
> in other tiddlers when I hit /.
>
> In other parts of the UI, I have essentially inserted the subfilter "
> get-stream-root[]" everywhere, so that the recent tab, the sidebar 
> searches, etc only show root tiddlers in the results. 
>
> I think one of the other members in the community here configured the 
> names of node tiddlers to be prefixed with $:/ which makes them system 
> tiddlers, which effectively hides them from most searches... another option 
> worth considering and simpler to setup.
>
> On Thu, 22 Jul 2021 at 15:02, Saq Imtiaz  wrote:
>
>>
>> Is there a search tool or plugin that works with streams? Streams is neat 
>>> to take notes with, but searching is problematic since the default search 
>>> shows you only the titles. Possibly someone has already written a custom 
>>> search? 
>>>
>>
>> @Mark S:
>>
>> I don't think there is a good generalized solution for this yet. Needs 
>> vary depending on people's workflow and title naming setup within Streams. 
>> I have posted a search customization for a specific users workflow at one 
>> point to show what customizations for search might look like.
>>
>> If you just want search results to show the root tiddler title as opposed 
>> to the titles of individual nodes, the attached file adds a tab to the 
>> search results to do that. If I remember correctly, title matches are 
>> returned unchanged whereas text matches only return the root tiddler.
>>
>> The missing piece is of course that once you find and open the root 
>> tiddler, it can be tricky finding the text you searched for within that 
>> stream.
>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/1ab33144-87d6-4d95-8c77-e05565891025n%40googlegroups.com
>>  
>> 

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@Mark S; I particularly like the command palette
 plugin for searches.

Please note it is not designed for Streams, but can be made to work quite
nicely with it because the search steps are highly configurable through
the  $:/plugins/souk21/commandpalette/CommandPaletteSearchSteps tiddler.
Here's an example of what I use at work; you'll notice I give precedence to
title matches (they'll be at the top of the results) and use the
get-streams-root[] filter extensively. The command palette adds a category (
hint) in the search results which I find helpful.

{
"steps": [
  {"filter":
"[!is[system]tag[todo]search:title:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
"hint": "todo (titles)", "caret": "42"},
  {"filter":
"[!is[system]tag[todo]search:text:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]",
"hint": "todo (text)", "caret": "41"},
  {"filter":
"[!is[system]tag[Meeting]search:title:literal[]!sort[title]]", "hint":
"meetings (main)", "caret": "45"},
  {"filter":
"[!is[system]tag[Journal]search:title:literal[]!sort[title]first[2]]",
"hint": "meetings (titles)", "caret": "45"},
  {"filter":
"[!is[system]tag[Journal]search:text:literal[]get-stream-root[]!sort[title]]",
"hint": "meetings (text)", "caret": "44"},
  {"filter":
"[!is[system]search:title:literal[]get-stream-root[]]", "hint":
"others (titles)", "caret": "33"},
  {"filter":
"[!is[system]search:text:literal[]get-stream-root[]]", "hint": "others
(text)", "caret": "32"},
  {"filter":
"[!is[system]tag[todo]search:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]tag[done]]",
"hint": "completed", "caret": "42"},
  {"filter":
"[!is[system]search::literal[]get-stream-root[]]", "hint": "all",
"caret": "28"}
]
}

I have configured the command palette to fire on a single key shortcut (/).
Whilst TiddlyWiki offers keyboard shortcuts, they fire everywhere out of
the box, even within text boxes (not ideal for single key shortcuts!), so
my setup relies on the mousetrap

plugin: hitting / in a text box does not fire the command palette. I am
working on a tweak that will have a richer set of search steps
configuration, so that I can invoke the command palette to search for tasks
(I use projectify ) using shift+/ and to search
in other tiddlers when I hit /.

In other parts of the UI, I have essentially inserted the subfilter "
get-stream-root[]" everywhere, so that the recent tab, the sidebar
searches, etc only show root tiddlers in the results.

I think one of the other members in the community here configured the names
of node tiddlers to be prefixed with $:/ which makes them system tiddlers,
which effectively hides them from most searches... another option worth
considering and simpler to setup.

On Thu, 22 Jul 2021 at 15:02, Saq Imtiaz  wrote:

>
> Is there a search tool or plugin that works with streams? Streams is neat
>> to take notes with, but searching is problematic since the default search
>> shows you only the titles. Possibly someone has already written a custom
>> search?
>>
>
> @Mark S:
>
> I don't think there is a good generalized solution for this yet. Needs
> vary depending on people's workflow and title naming setup within Streams.
> I have posted a search customization for a specific users workflow at one
> point to show what customizations for search might look like.
>
> If you just want search results to show the root tiddler title as opposed
> to the titles of individual nodes, the attached file adds a tab to the
> search results to do that. If I remember correctly, title matches are
> returned unchanged whereas text matches only return the root tiddler.
>
> The missing piece is of course that once you find and open the root
> tiddler, it can be tricky finding the text you searched for within that
> stream.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/1ab33144-87d6-4d95-8c77-e05565891025n%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/CAAY2DnMyHGFYPE8xKTVBWzNVwE7D0cNqiM7kUt%3DdEV-i%3DLu9%3

[tw5] Re: Excising Large Outlines in TW

[Saq Imtiaz]

Mark you can save a plugin tiddler as a 
folder: https://links.tiddlywiki.com/urls/4b5e9c4afc6923035ef9/

Otherwise you can drag and drop the plugin to your wiki and import it and 
it will work, though it will only be installed for that specific wiki to 
which you dragged it.

On Thursday, July 22, 2021 at 9:57:01 PM UTC+2 mark.cu...@gmail.com wrote:

> @David
> Is there a plugin folder to download. I'm not convinced I know how to 
> install your plugin otherwise. I'm running TW via Node.js.
> On Wednesday, July 21, 2021 at 3:44:45 PM UTC-4 Mark Cubberley wrote:
>
>> @David
>> I have been keeping my eye on the Subsume threads and this plugin may be 
>> what I'm looking for. Between my naiveté of TW and, for the moment, a 
>> rather nebulous pedagogical project, I am not convinced I know what I'm 
>> asking, but I appreciate the reply nonetheless.
>>
>> @ Mark S.
>> You are correct. More often than not, there IS too much material and I my 
>> intent is not to add more to an already dense curriculum. I see systems 
>> thinking as pedagogical strategy/framework for my teaching. (Systems 
>> thinking in chemical education is new to me and to chemical education for 
>> that matter.) I do not yet know what content I may have to sacrifice to use 
>> this pedagogy, nor if the loss of this content compromises the learning 
>> objectives of the course(s). I am hoping to figure all this out in a public 
>> facing TW using these concept outlines as a knowledge base.
>> On Wednesday, July 21, 2021 at 2:04:41 PM UTC-4 Mark S. wrote:
>>
>>> The official slicer edition does pretty much what you describe 
>>> https://tiddlywiki.com/editions/text-slicer/ .
>>> But it uses a complicated relationship between the resulting tiddlers 
>>> that may be difficult to manipulate.
>>>
>>> Notowritey (https://marxsal.github.io/various/notowritey.html) allows 
>>> you to split large texts using a regular expression. You can then 
>>> manipulate items into a hierarchical arrangement in a manner similar to a 
>>> regular outliner. The relationship is based on simple listing and tagging.
>>>
>>> I would imagine for a systems approach, you would have to add a great 
>>> deal more of material. What I remember about chemistry is that they already 
>>> give you too much material to remember and often assume you are familiar 
>>> with processes and techniques that you have never encountered anywhere. As 
>>> if someone just ripped pages out of your textbook and threw them away. 
>>> Trying to see how you could fit MORE into the curriculum seems somewhat 
>>> unkind.
>>>
>>> Another Mark
>>>
>>> On Wednesday, July 21, 2021 at 10:06:42 AM UTC-7 mark.cu...@gmail.com 
>>> wrote:
>>>
 I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell 
 over the last several weeks. Most of this time has been just getting stuff 
 into TW and seeing what happens (or doesn't and trying to figure out why). 
 I have not spent any time creating, connecting, etc.. The product of my 
 work thus far is here.

 I have two large outlines (GeneralChemistryACCMOutline and 
 OrganicChemistryACCMOutline) that delineate anchoring concept content 
 maps  for most of the 
 undergraduate chemistry I teach. The hierarchy of these outlines is 
 identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
 differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
 Details).

 I need to excise these outlines and then add open educational resources 
 (text, links to videos, images, and simulations, exercises, etc.) to the 
 resulting tiddlers.

 I am interested in your thoughts on how I might excise these outlines 
 in a (unique?) way that leverages TW’s utility/flexibility as a 
 content-management system considering:

1. The order of Level 1 Big Ideas is consistent with the sequence 
of instruction.
2. I would like to somehow leverage TW and the connected, 
context-free facts derived from these outlines to move away from a 
reductionist approach to teaching and learning to a systems approach 
 to teaching and 
learning. 
3. I do not yet know specifically how I am going to use this 
resource in a teaching setting.
4. I am new to TW…

 Thanks for your help.

 Mark

>>>

-- 
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/a5c8c4f9-eef1-401f-9c63-de24c5200a44n%40googlegroups.com.

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Saq Imtiaz]

>
>  If I get some time in the next couple months and nobody else does it, 
> maybe I will take a look at how to get started with TW core development.
>
>
Would be happy to answer any questions you might have along those lines.

-- 
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/b78c98c7-d4af-4bfd-90c0-1e4f7f9b3cc2n%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

You can see your corresponding local time at the following link:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=TiddlyWiki+Community+Call+and+File+Uploads+Plugin&iso=20210817T18&p1=195&ah=1&am=30

-- 
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/e26457d8-7edc-4b70-b35b-573706e40e82n%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

Apologies Soren, I should have specified in UTC as well. CET is indeed 
UTC+2.

So the community call is at August 17th at 16:00 UTC

You can see your corresponding local time here .

On Thursday, July 22, 2021 at 10:18:45 PM UTC+2 Soren Bjornstad wrote:

> Saq,
>
> To clarify for those of us who are not as familiar with European time 
> zones, is this UTC+2 because it is summer?
> On Thursday, July 22, 2021 at 2:33:18 PM UTC-5 saq.i...@gmail.com wrote:
>
>> We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
>> myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
>> Syncers, Upload Plugin, & Community Forum - Zoom 
>>
>> I hope some of you will be able to join us for what I think will be a 
>> very interesting discussion. Please register for the event at the link 
>> above.
>>
>> The call will include:
>>
>>- a progress update on my work on the *Uploads plugin* funded by Open 
>>Collective
>>- a summary of some rather exciting and promising avenues for core 
>>development in the areas of *Savers and Syncers* that has come out of 
>>discussions around the Uploads plugin
>>- an update on the *Open Collective* model for funding TiddlyWiki 
>>work and what we have learned from it thus far
>>- some news from Jeremy and Boris regarding improvements to 
>>TiddlyWiki *community infrastructure*.
>>
>> I have been slowly working away on the TiddlyWiki file uploads plugin as 
>> was previously announced 
>> . 
>> The majority of the work thus far has consisted of brainstorming around the 
>> architecture and some very involved but promising and productive 
>> discussions with Jeremy around how such a plugin would integrate with the 
>> core, and the direction that the core might take in the future with regards 
>> to saving and syncing mechanisms. 
>>
>> In particular we have identified some exciting opportunities to explore 
>> in due course for a rethinking of the saver and syncer mechanisms that may 
>> amongst other things eventually make file uploads a core TiddlyWiki ability 
>> alongside saving and syncing and static file publishing.
>>
>> This has necessitated a change in approach to the File Uploads plugin so 
>> as to not introduce changes to the TiddlyWiki core at this time which may 
>> clash with the long term direction of development, and still make the 
>> Uploads plugin available in a timely manner for those that need this 
>> functionality today. I currently have a minimal working prototype that 
>> uploads images imported into TiddlyWiki to Fission, though with no UI or 
>> error handling as of yet and desperately in need of some heavy refactoring 
>> to better be able to support different storage back ends. I hope to present 
>> a demo of an early version of the plugin on the call.
>>
>> I would like to take the opportunity here to thank Boris and Fission. 
>> Despite Boris having chipped in for the vast majority of the funding for 
>> this plugin as it is something he needs in his own TiddlyWiki usage, not 
>> only has he been patient and supportive as we focus on long term core 
>> planning first, but Fission has actively been facilitating those 
>> discussions.
>>
>> Regards,
>> 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 email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/83df5210-a937-4272-bf60-169f3f20a7d1n%40googlegroups.com.

[tw5] Re: What other tools compliment TiddlyWiki well? [discussion]

[Si]

Thanks for the responses.

I like Keep, very nice level of simplicity and pleasant to use. Personally 
I try to avoid Google stuff where I can, but I did notice this very nice 
keep-style Android app that has recently appeared on Fdroid: 
https://github.com/msoultanidis/quillnote. Unfortunately it's Android only, 
but I'll be keeping an eye on it in case they add a way to sync the notes 
to a computer as markdown files.

@Tones 

> I don't concur with your statement Si, as I think I said before  *In my 
opinion a major weakness of TiddlyWiki is that it is not well suited to 
quickly capturing information on the fly with minimal friction.*

I wouldn't want to spend much time defending my view, as I think what 
does/doesn't count as friction is pretty subjective. My biggest problems 
are on mobile, where saving a single file wiki with Tiddloid takes too long 
for me to ever really feel like using it. I had forgotten about 
Projectify's quick-add feature though, which I agree is very useful for 
quick-capture.

> I did look into getting tiddlywiki into a browser side bar in the past. I 
believed it worked in FireFox, but if not universal it is less interesting. 

There are a few Firefox extensions for doing this, but I couldn't get any 
to work with a local file. Perhaps they will work with the node.js version. 
Vivaldi has a built in feature for doing this which works very nicely with 
TiddlyWiki: https://help.vivaldi.com/desktop/panels/web-panels/
On Thursday, 22 July 2021 at 05:35:35 UTC+1 TW Tones wrote:

> Keep is popular.
>
> I did look into getting tiddlywiki into a browser side bar in the past. I 
> believed it worked in FireFox, but if not universal it is less interesting. 
> That is the advantage of keep if you use a few of googles tools.
>
> Tones
>
> On Thursday, 22 July 2021 at 13:34:37 UTC+10 cj.v...@gmail.com wrote:
>
>> I'm thinking it largely depends on the "ecosystem" one may be living in.
>>
>> Seeing as I've sold my soul to Google, Google Keep is my goto quick note 
>> taker.
>>
>> I can access the full screen Google Keep, sidebar Google Keep when I'm in 
>> the other Google Apps, and have the Google Keep Chrome Extension, to 
>> quickly take notes while viewing some web page.
>>
>> So quick note taking for some heavy-duty note making in TiddlyWiki later.
>>
>> Mind you, I only ever use my Chromebook.  I never use my "smart" phone 
>> for anything other than text and phone.
>>
>> Well, it is always a work-in-progress.
>>
>> On Wednesday, July 21, 2021 at 4:10:04 PM UTC-3 Si wrote:
>>
>>> This question was prompted by a discussion over in the thread on 
>>> incremental note-taking 
>>> .
>>>
>>> In my opinion a major weakness of TiddlyWiki is that it is not well 
>>> suited to quickly capturing information on the fly with minimal friction.
>>>
>>> For this reason I use another app as an "inbox" for quick ideas and 
>>> tasks, which I process later on. Currently I use Evernote, but I'm 
>>> currently in the process of looking for something else (would love to hear 
>>> suggestions for a good replacement). The number one contender at the moment 
>>> is Joplin , but I'm tempted by the 
>>> purity of using text/markdown files if I can find a good way to handle them 
>>> on Android.
>>>
>>> Anyway I thought it would be interesting to prompt a discussion by 
>>> asking the more general question: *What apps or tools do you use that 
>>> you feel compliment TiddlyWiki well?* *What does your workflow look 
>>> like?*
>>>
>>> It doesn't matter the domain - note-taking and productivity are the 
>>> obvious categories, but please be free to share any tool you use in tandem 
>>> with TiddlyWiki.
>>>
>>

-- 
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/295ee80f-44d6-4559-a174-9ba7d3874ebfn%40googlegroups.com.

[tw5] Re: TiddlyWiki Community Call and File Uploads Plugin

[Soren Bjornstad]

Saq,

To clarify for those of us who are not as familiar with European time 
zones, is this UTC+2 because it is summer?
On Thursday, July 22, 2021 at 2:33:18 PM UTC-5 saq.i...@gmail.com wrote:

> We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
> myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
> Syncers, Upload Plugin, & Community Forum - Zoom 
>
> I hope some of you will be able to join us for what I think will be a very 
> interesting discussion. Please register for the event at the link above.
>
> The call will include:
>
>- a progress update on my work on the *Uploads plugin* funded by Open 
>Collective
>- a summary of some rather exciting and promising avenues for core 
>development in the areas of *Savers and Syncers* that has come out of 
>discussions around the Uploads plugin
>- an update on the *Open Collective* model for funding TiddlyWiki work 
>and what we have learned from it thus far
>- some news from Jeremy and Boris regarding improvements to TiddlyWiki 
> *community 
>infrastructure*.
>
> I have been slowly working away on the TiddlyWiki file uploads plugin as 
> was previously announced 
> . 
> The majority of the work thus far has consisted of brainstorming around the 
> architecture and some very involved but promising and productive 
> discussions with Jeremy around how such a plugin would integrate with the 
> core, and the direction that the core might take in the future with regards 
> to saving and syncing mechanisms. 
>
> In particular we have identified some exciting opportunities to explore in 
> due course for a rethinking of the saver and syncer mechanisms that may 
> amongst other things eventually make file uploads a core TiddlyWiki ability 
> alongside saving and syncing and static file publishing.
>
> This has necessitated a change in approach to the File Uploads plugin so 
> as to not introduce changes to the TiddlyWiki core at this time which may 
> clash with the long term direction of development, and still make the 
> Uploads plugin available in a timely manner for those that need this 
> functionality today. I currently have a minimal working prototype that 
> uploads images imported into TiddlyWiki to Fission, though with no UI or 
> error handling as of yet and desperately in need of some heavy refactoring 
> to better be able to support different storage back ends. I hope to present 
> a demo of an early version of the plugin on the call.
>
> I would like to take the opportunity here to thank Boris and Fission. 
> Despite Boris having chipped in for the vast majority of the funding for 
> this plugin as it is something he needs in his own TiddlyWiki usage, not 
> only has he been patient and supportive as we focus on long term core 
> planning first, but Fission has actively been facilitating those 
> discussions.
>
> Regards,
> 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 email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/7d2a6672-464d-453b-bedd-74006c636b5cn%40googlegroups.com.

[tw5] Re: Simplest way to list all tiddlers that transclude the current tiddler?

[Soren Bjornstad]

This isn't supported in core currently, though there's a pull request about 
it that needs a bunch of work to be mergeable that I keep harping on 
because I want this too. :-) If I get some time in the next couple months 
and nobody else does it, maybe I will take a look at how to get started 
with TW core development.

In the meantime, the relink plugin implements its own filter operator for 
this, though as I understand, it is undocumented and might change behavior 
in future versions of Relink. See this recent thread 
.

On Thursday, July 22, 2021 at 12:29:24 PM UTC-5 evanwh...@gmail.com wrote:

> Hey everyone, this is my first post here, sorry if I'm asking a common 
> question.
>
> Basically I have constructed a footer that displays all backlinks of the 
> current tiddler, and I want to extend it to also display all transclusions 
> as well. 
>
> I know this is possible because I use the relink plugin, and it seems to 
> have similar functionality. I just can't figure out how to harness it for 
> myself!
>
> My footer currently looks like this:
>
> 
>   Backlinks: 
>   
>
>   
> <$list filter="[all[current]backlinks[]sort[title]]" emptyMessage="">
>   <$link to={{!!title}}><$view field="title"/>
>   
> 
>   
> 
>
> Let me know what you think. Thanks everyone!
>

-- 
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/40f121b2-e315-402e-92e7-745c09771619n%40googlegroups.com.

[tw5] Re: Excising Large Outlines in TW

[Mark Cubberley]

@David
Is there a plugin folder to download. I'm not convinced I know how to 
install your plugin otherwise. I'm running TW via Node.js.
On Wednesday, July 21, 2021 at 3:44:45 PM UTC-4 Mark Cubberley wrote:

> @David
> I have been keeping my eye on the Subsume threads and this plugin may be 
> what I'm looking for. Between my naiveté of TW and, for the moment, a 
> rather nebulous pedagogical project, I am not convinced I know what I'm 
> asking, but I appreciate the reply nonetheless.
>
> @ Mark S.
> You are correct. More often than not, there IS too much material and I my 
> intent is not to add more to an already dense curriculum. I see systems 
> thinking as pedagogical strategy/framework for my teaching. (Systems 
> thinking in chemical education is new to me and to chemical education for 
> that matter.) I do not yet know what content I may have to sacrifice to use 
> this pedagogy, nor if the loss of this content compromises the learning 
> objectives of the course(s). I am hoping to figure all this out in a public 
> facing TW using these concept outlines as a knowledge base.
> On Wednesday, July 21, 2021 at 2:04:41 PM UTC-4 Mark S. wrote:
>
>> The official slicer edition does pretty much what you describe 
>> https://tiddlywiki.com/editions/text-slicer/ .
>> But it uses a complicated relationship between the resulting tiddlers 
>> that may be difficult to manipulate.
>>
>> Notowritey (https://marxsal.github.io/various/notowritey.html) allows 
>> you to split large texts using a regular expression. You can then 
>> manipulate items into a hierarchical arrangement in a manner similar to a 
>> regular outliner. The relationship is based on simple listing and tagging.
>>
>> I would imagine for a systems approach, you would have to add a great 
>> deal more of material. What I remember about chemistry is that they already 
>> give you too much material to remember and often assume you are familiar 
>> with processes and techniques that you have never encountered anywhere. As 
>> if someone just ripped pages out of your textbook and threw them away. 
>> Trying to see how you could fit MORE into the curriculum seems somewhat 
>> unkind.
>>
>> Another Mark
>>
>> On Wednesday, July 21, 2021 at 10:06:42 AM UTC-7 mark.cu...@gmail.com 
>> wrote:
>>
>>> I have been using Soren’s Grok TiddlyWiki and his Zettelkasten shell 
>>> over the last several weeks. Most of this time has been just getting stuff 
>>> into TW and seeing what happens (or doesn't and trying to figure out why). 
>>> I have not spent any time creating, connecting, etc.. The product of my 
>>> work thus far is here.
>>>
>>> I have two large outlines (GeneralChemistryACCMOutline and 
>>> OrganicChemistryACCMOutline) that delineate anchoring concept content 
>>> maps  for most of the 
>>> undergraduate chemistry I teach. The hierarchy of these outlines is 
>>> identical at Level 1 (Big Ideas) and Level 2 (Enduring Understandings) and 
>>> differ at Level 3 (Subdisciplinary Articulations) and Level 4 (Content 
>>> Details).
>>>
>>> I need to excise these outlines and then add open educational resources 
>>> (text, links to videos, images, and simulations, exercises, etc.) to the 
>>> resulting tiddlers.
>>>
>>> I am interested in your thoughts on how I might excise these outlines in 
>>> a (unique?) way that leverages TW’s utility/flexibility as a 
>>> content-management system considering:
>>>
>>>1. The order of Level 1 Big Ideas is consistent with the sequence of 
>>>instruction.
>>>2. I would like to somehow leverage TW and the connected, 
>>>context-free facts derived from these outlines to move away from a 
>>>reductionist approach to teaching and learning to a systems approach 
>>> to teaching and 
>>>learning. 
>>>3. I do not yet know specifically how I am going to use this 
>>>resource in a teaching setting.
>>>4. I am new to TW…
>>>
>>> Thanks for your help.
>>>
>>> Mark
>>>
>>

-- 
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/0b824948-b9c3-4ca4-86bd-a99448cfd1fbn%40googlegroups.com.

[tw5] TiddlyWiki Community Call and File Uploads Plugin

[Saq Imtiaz]

We will be having a *TiddlyWiki Community call* with Jeremy, Boris and 
myself on August 17th at 6pm CET: TiddlyWiki Community: Core Savers & 
Syncers, Upload Plugin, & Community Forum - Zoom 

I hope some of you will be able to join us for what I think will be a very 
interesting discussion. Please register for the event at the link above.

The call will include:

   - a progress update on my work on the *Uploads plugin* funded by Open 
   Collective
   - a summary of some rather exciting and promising avenues for core 
   development in the areas of *Savers and Syncers* that has come out of 
   discussions around the Uploads plugin
   - an update on the *Open Collective* model for funding TiddlyWiki work 
   and what we have learned from it thus far
   - some news from Jeremy and Boris regarding improvements to TiddlyWiki 
*community 
   infrastructure*.

I have been slowly working away on the TiddlyWiki file uploads plugin as 
was previously announced 
. The 
majority of the work thus far has consisted of brainstorming around the 
architecture and some very involved but promising and productive 
discussions with Jeremy around how such a plugin would integrate with the 
core, and the direction that the core might take in the future with regards 
to saving and syncing mechanisms. 

In particular we have identified some exciting opportunities to explore in 
due course for a rethinking of the saver and syncer mechanisms that may 
amongst other things eventually make file uploads a core TiddlyWiki ability 
alongside saving and syncing and static file publishing.

This has necessitated a change in approach to the File Uploads plugin so as 
to not introduce changes to the TiddlyWiki core at this time which may 
clash with the long term direction of development, and still make the 
Uploads plugin available in a timely manner for those that need this 
functionality today. I currently have a minimal working prototype that 
uploads images imported into TiddlyWiki to Fission, though with no UI or 
error handling as of yet and desperately in need of some heavy refactoring 
to better be able to support different storage back ends. I hope to present 
a demo of an early version of the plugin on the call.

I would like to take the opportunity here to thank Boris and Fission. 
Despite Boris having chipped in for the vast majority of the funding for 
this plugin as it is something he needs in his own TiddlyWiki usage, not 
only has he been patient and supportive as we focus on long term core 
planning first, but Fission has actively been facilitating those 
discussions.

Regards,
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 email 
to tiddlywiki+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/86426dff-75ea-49b8-9840-f899adbbe485n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[springer]

Jeremy and all,

I've played around with the updated prerelease file, starting by importing 
all the tiddlers from the "broken" version. So far, saves on github are 
going fine.

Only one (!) major glitch. If you name a field with a double-angle-bracket 
expression (Who would do such a thing?!), Shiraz gets confused. (Probably 
other tools would get confused too, but Shiraz is the thing I've been 
testing.)

For one proof-of-concept, I created a little ViewTemplate footer that 
provides a dynamic table overview of any tiddlers that use the current 
tiddler's title as a (non-empty) field name.

I do see some minor glitches with ViewTemplates (contents not looking as 
they should, conditional filters not behaving as they should), but it's 
possible my own limited trouble-shooting skills are to blame. It's also 
possible that some interaction with one or more <> is to blame.

If anyone wants to play around see here: 
https://springerspandrel.github.io/tw/new-json-tw-experiment.html

-Springer
On Thursday, July 22, 2021 at 11:57:34 AM UTC-4 jeremy...@gmail.com wrote:

>
> On 21 Jul 2021, at 21:11, Saq Imtiaz  wrote:
>
> I believe this check for field names is the cause:
>
>
> https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
>
>
> Thanks for your help with this, the problem with fields with spaces in 
> their names has been resolved here:
>
>
> https://github.com/Jermolene/TiddlyWiki5/commit/19fd5ca5f26f798742e411453b30ad467b101a50
>
> The update will be live at https://tiddlywiki.com/prerelease shortly,
>
> Best wishes
>
> 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/f46c2fae-b8e0-4571-b325-6930295224cfn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

> Is there a search tool or plugin that works with streams? Streams is neat 
> to take notes with, but searching is problematic since the default search 
> shows you only the titles. Possibly someone has already written a custom 
> search? 
>

@Mark S:

I don't think there is a good generalized solution for this yet. Needs vary 
depending on people's workflow and title naming setup within Streams. I 
have posted a search customization for a specific users workflow at one 
point to show what customizations for search might look like.

If you just want search results to show the root tiddler title as opposed 
to the titles of individual nodes, the attached file adds a tab to the 
search results to do that. If I remember correctly, title matches are 
returned unchanged whereas text matches only return the root tiddler.

The missing piece is of course that once you find and open the root 
tiddler, it can be tricky finding the text you searched for within that 
stream.

-- 
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/1ab33144-87d6-4d95-8c77-e05565891025n%40googlegroups.com.


$__streams_addons_ui_SearchResultList.json
Description: application/json

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@walt yes precisely, the existing two options would remain with slightly
better wording. The two new options would take the output of the
conversion, place it in the root tiddler's text field, and remove any
streams nodes recursively (cascade). The tags (and other fields) of the
root tiddler would be preserved. Tags or fields of node tiddlers would be
ignored & lost.

On Thu, 22 Jul 2021 at 13:40, ludwa6  wrote:

> My feedback @Fred depends on what you mean by "collapse and replace
> stream" options -presuming the "fuse into new tiddler" options stand as
> they are now, right?
>
> I only know how it's working now -which does involve a few steps, i.e.:
>
>1. Push the button (1st one on L, not the next to R, which is an
>artifact that we can do without) and select format option;
>2. Move off this (tiddlername)_Fused tiddler to the parent of Stream,
>and delete (confirming deletion of nodes as well as tiddler, in the popup
>warning msg);
>3. Go back to (tiddlername)_Fused tiddler and rename w/o "_Fused"
>suffix to name of the deleted parent.
>4. In case the parent had a tag (e.g.  "Journal" tids -my most common
>use-case for this), must reapply such tag(s)
>
> If you could collapse steps 2, 3 AND 4 into step 1, that would be the
> ultimate UX for me...
> ... but hey Fred: the user workflow is not at all heavy as it stands!
>
> /walt
>
>
> On Thursday, July 22, 2021 at 4:28:33 PM UTC+1 fred@gmail.com wrote:
>
>> @walt; I'll experiment with two additional options to the popup menu, to
>> save you a step (and fix the position bug) this evening, if you think that
>> helps your use case
>>
>> I am thinking:
>>
>>- fuse into new tiddler using bullets
>>- fuse into new tiddler using numbers
>>- collapse and replace stream using bullets
>>- collapse and replace stream using numbers
>>
>>
>> (with confirmation prompt for the latter two)
>>
>>
>>
>> On Thu, 22 Jul 2021 at 11:01, ludwa6  wrote:
>>
>>> Cool! the final step (i.e. cleanup) needed to flatten a Stream of nodes
>>> into a single tiddler, while preserving hierarchal presentation in readily
>>> portable form.
>>> I'll be using the heck out of this.
>>> Nice job of scaffold-building, @Saq / @Jan / @Fred ; you guys rock!
>>>
>>> /walt
>>>
>>>
>>> On Thursday, July 22, 2021 at 2:58:02 PM UTC+1 saq.i...@gmail.com wrote:
>>>

 Also need to find an easy way to delete all the node-tiddlers rendered
> superfluous, once i flatten using your modal ; this is the one function of
> Jan's addon that i miss...
>
> Delete the root tiddler the way you would delete any other tiddler.
 You will be prompted to delete it's nodes as well.



>>> --
>>>
>> You received this message because you are subscribed to a topic in the
>>> Google Groups "TiddlyWiki" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> tiddlywiki+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/tiddlywiki/6d2c42b9-f03b-47f8-a224-1957520366cen%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/b7152a98-70a0-4da2-adb6-8b5abba03cf9n%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/CAAY2DnNA0FcWKik%3DXJ470z--oB1gaVXqHBkRmAS9Px-dQhEkQg%40mail.gmail.com.

[tw5] Re: tidders created this week

[Stobot]

WOW - agree with Soren, this is HUGE - this will remove the need for sooo 
many <$wikify> widgets!

On Thursday, July 22, 2021 at 7:59:34 AM UTC-4 Soren Bjornstad wrote:

> On Wednesday, July 21, 2021 at 9:58:33 PM UTC-5 TW Tones wrote:
>
>> From the pre-release this feature should make it even simpler
>>  New in: 5.2.0 Literal macro parameters are supported 
>> . For example: 
>> [].
>>
>
> Ooh, that's slick, looking forward to it!
>

-- 
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/304d9159-653a-4c86-bee8-3397275f0e4fn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

['Mark S.' via TiddlyWiki]

Is there a search tool or plugin that works with streams? Streams is neat 
to take notes with, but searching is problematic since the default search 
shows you only the titles. Possibly someone has already written a custom 
search? 

>
>>>

-- 
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/6cff3995-bfae-443f-82f4-d0ae09f15c79n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[ludwa6]

My feedback @Fred depends on what you mean by "collapse and replace stream" 
options -presuming the "fuse into new tiddler" options stand as they are 
now, right? 

I only know how it's working now -which does involve a few steps, i.e.:

   1. Push the button (1st one on L, not the next to R, which is an 
   artifact that we can do without) and select format option; 
   2. Move off this (tiddlername)_Fused tiddler to the parent of Stream, 
   and delete (confirming deletion of nodes as well as tiddler, in the popup 
   warning msg); 
   3. Go back to (tiddlername)_Fused tiddler and rename w/o "_Fused" suffix 
   to name of the deleted parent.
   4. In case the parent had a tag (e.g.  "Journal" tids -my most common 
   use-case for this), must reapply such tag(s)

If you could collapse steps 2, 3 AND 4 into step 1, that would be the 
ultimate UX for me...
... but hey Fred: the user workflow is not at all heavy as it stands!

/walt


On Thursday, July 22, 2021 at 4:28:33 PM UTC+1 fred@gmail.com wrote:

> @walt; I'll experiment with two additional options to the popup menu, to 
> save you a step (and fix the position bug) this evening, if you think that 
> helps your use case
>
> I am thinking:
>
>- fuse into new tiddler using bullets
>- fuse into new tiddler using numbers
>- collapse and replace stream using bullets
>- collapse and replace stream using numbers
>
>
> (with confirmation prompt for the latter two)
>
>
>
> On Thu, 22 Jul 2021 at 11:01, ludwa6  wrote:
>
>> Cool! the final step (i.e. cleanup) needed to flatten a Stream of nodes 
>> into a single tiddler, while preserving hierarchal presentation in readily 
>> portable form.  
>> I'll be using the heck out of this.
>> Nice job of scaffold-building, @Saq / @Jan / @Fred ; you guys rock!
>>
>> /walt
>>
>>
>> On Thursday, July 22, 2021 at 2:58:02 PM UTC+1 saq.i...@gmail.com wrote:
>>
>>>
>>> Also need to find an easy way to delete all the node-tiddlers rendered 
 superfluous, once i flatten using your modal ; this is the one function of 
 Jan's addon that i miss... 

 Delete the root tiddler the way you would delete any other tiddler. You 
>>> will be prompted to delete it's nodes as well.
>>>
>>>  
>>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/6d2c42b9-f03b-47f8-a224-1957520366cen%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/b7152a98-70a0-4da2-adb6-8b5abba03cf9n%40googlegroups.com.

[tw5] Simplest way to list all tiddlers that transclude the current tiddler?

[Evan Hackett]

Hey everyone, this is my first post here, sorry if I'm asking a common 
question.

Basically I have constructed a footer that displays all backlinks of the 
current tiddler, and I want to extend it to also display all transclusions 
as well. 

I know this is possible because I use the relink plugin, and it seems to 
have similar functionality. I just can't figure out how to harness it for 
myself!

My footer currently looks like this:


  Backlinks: 
  

  
<$list filter="[all[current]backlinks[]sort[title]]" emptyMessage="">
  <$link to={{!!title}}><$view field="title"/>
  

  


Let me know what you think. Thanks everyone!

-- 
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/433f935a-6acd-43fe-a2b5-4525c44b2b8bn%40googlegroups.com.

[tw5] Re: Seeking general feedback on Grok TiddlyWiki

[springer]

Soren,

I think I'm part of the target audience for Grok TiddlyWiki, despite being 
a long-time user. I have never given myself a systematic approach, and have 
instead always learned whatever bits I need to solve this or that 
problem-at-hand. I'm grateful for your learning tool, and am slowly working 
through it (systematically including nearly all exercises through Chapter 
Four, with skimming and selective reading past that, as I've had less time 
to devote recently). 

The organization seems helpful to me, though like many dabblers I have 
depth in some areas you call "advanced" and deficits in some basics. A few 
early portions feel too elementary for me, but I've worked through them 
anyway, partly to make sure I absorb technical terminology better (where I 
know how to do X but not what the ingredients are called), and partly 
because I am frequently surprised, even in early chapters, by what Tones 
calls the occasional "easter egg" of discovering a new thing.

I did have one frustrating rabbit-hole experience with the RubberDucking 
exercise, but it was anomalous (I was working on a clone of your book, 
which contained an error you have since fixed. On my version, you hadn't 
yet compensated for how you tucked various components into shadows. I 
"fixed" the exercise filter's punctuation correctly, but it still showed 
nothing. My Rubber Duck was not at all helpful until it suggested that I 
dial up the book at your url, where "Eureka!" the actual exercise prompt 
was different. I could email you the details, but it's not of general 
interest.)

I'm pretty sure my skills are improving, especially if I think half of a 
skill is having the right *concepts* for one's skills, and a cogent 
understanding of their scope and limits.

One thing I specifically appreciate is that a search for "boolean" on your 
book brought me to a helpful discussion. I had tried in vain to find 
"boolean" on tiddlywiki.com (where it appears only incidentally around 
"then" and else") and on https://tobibeer.github.io/tw/filters/  ... (Not 
getting any helpful hits at these two spots did make me feel pretty crazy!) 
Finding a direct discussion of how boolean operations need to be 
approached, for filters, is the kind of thing many users might appreciate. 
(Note: I'd add words like "conjunction" and "disjunction" to your 
discussion, to aid searchability. The word "or" is of course unhelpfully 
too short -- with too many false positives -- for those who bring logical 
concepts to TiddlyWiki but aren't yet oriented to its operators.)

-Springer
On Wednesday, July 21, 2021 at 9:56:56 AM UTC-4 Soren Bjornstad wrote:

> Hi everyone,
>
> I know quite a few people on here have been reading at least some of my 
> book Grok TiddlyWiki . While I've 
> gotten quite a bit of specific feedback submitted through the built-in 
> feedback mechanism, I've been coming up short on overall impressions and 
> significance beyond "thanks so much for this book." If you've looked at the 
> book and you have a few moments, I'd love to know what you think. For 
> instance:
>
>- Is the book organized effectively?
>- What parts have you read/worked through?
>- How have you been using the book? Have you done some of the 
>exercises and flashcards? Do they work? (I'm particularly interested in 
>this question because I'd love to iterate and build more resources like 
>this one in the future.)
>- How have your TiddlyWiki skills improved, if they have?
>- Any other thoughts?
>
> If there's anything you don't want to share publicly, feel free to email 
> it directly to me at contact (at) sorenbjornstad.com.
>
> Much appreciated,
> Soren
>

-- 
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/d684dabc-0b58-41c0-b6c2-0fe6a86c0813n%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[Jeremy Ruston]

> On 21 Jul 2021, at 21:11, Saq Imtiaz  wrote:
> 
> I believe this check for field names is the cause:
> 
> https://github.com/Jermolene/TiddlyWiki5/blob/d455072f13dd00955ae82d62d2d6e44581bdba9e/boot/boot.js#L1606
>  
> 
Thanks for your help with this, the problem with fields with spaces in their 
names has been resolved here:

https://github.com/Jermolene/TiddlyWiki5/commit/19fd5ca5f26f798742e411453b30ad467b101a50
 


The update will be live at https://tiddlywiki.com/prerelease 
 shortly,

Best wishes

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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/EA5BB628-46D7-43E4-A113-B56DCC3A4F72%40gmail.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@walt; I'll experiment with two additional options to the popup menu, to
save you a step (and fix the position bug) this evening, if you think that
helps your use case

I am thinking:

   - fuse into new tiddler using bullets
   - fuse into new tiddler using numbers
   - collapse and replace stream using bullets
   - collapse and replace stream using numbers


(with confirmation prompt for the latter two)



On Thu, 22 Jul 2021 at 11:01, ludwa6  wrote:

> Cool! the final step (i.e. cleanup) needed to flatten a Stream of nodes
> into a single tiddler, while preserving hierarchal presentation in readily
> portable form.
> I'll be using the heck out of this.
> Nice job of scaffold-building, @Saq / @Jan / @Fred ; you guys rock!
>
> /walt
>
>
> On Thursday, July 22, 2021 at 2:58:02 PM UTC+1 saq.i...@gmail.com wrote:
>
>>
>> Also need to find an easy way to delete all the node-tiddlers rendered
>>> superfluous, once i flatten using your modal ; this is the one function of
>>> Jan's addon that i miss...
>>>
>>> Delete the root tiddler the way you would delete any other tiddler. You
>> will be prompted to delete it's nodes as well.
>>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/6d2c42b9-f03b-47f8-a224-1957520366cen%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/CAAY2DnPy0Vhivz%2B0axfUy1km7DET%3DYJL2KRgtVvbDOwp8MtdCA%40mail.gmail.com.

[tw5] Re: Getting relink to prevent obsolete permalinks

[springer]

Tones,

This again is a place where different users may have different needs. I 
love the fact that if I share a permalink, the #TiddlerTitle at the end is 
not an indecipherable UID, but something recognizable and meaningful to the 
recipient (and even to myself, going back into my emails and recognizing 
what I shared). 

And as much as you may "choose my tiddler names well enough when needed so 
they need not change in future",  renaming a tiddler is not always a matter 
of realizing that you failed to have foresight the first time around. (My 
reason for invoking the Bombay to Mumbai change -- or Bruce to Caitlin if 
you prefer -- is that the world *about* which we take and share notes does 
not always cater to our desire for stability. ;)

I do realize that even without changing relink, we could mitigate obsolete 
permalinks (when we are aware of them) by setting up a ViewTemplate that 
works with a "formerly" field (or maybe just with a alias and aliases 
field), to transclude or redirect when the old permalink lands on an 
obsolete tiddler. 

-Springer
On Wednesday, July 21, 2021 at 9:17:10 PM UTC-4 TW Tones wrote:

> Springer et al,
>
> Forgive me for repeating myself, although a lot of interesting ideas, I 
> believe these to be *non-problems.* 
>
> A simple solution is available here. an Example would be an alternate 
> button to simple permalinks, I think someone else used a share icon. When 
> clicking this on a given tiddler, it would assign a next number to a field 
> in the tiddler (basically issuing a unique value field - not a UID or 
> serial or GUID) then use this field/number to uniquely identify the tiddler 
> shared, so it does not matter if it's title is renamed. Then generate a url 
> that instead searches for any (but only one) tiddler with that field value.
>
> If *anyone asks* I will build this share button soon.
>
> That is if someone wants to publish a robust permalink for a tiddler who's 
> title may change they use a built for purpose alternative to permalinks. 
> Perhaps the existing name permalinks is misleading, perhaps they should be 
> impermalinks.
>
> Here is a working example
> a tiddler with the "permalink" field=1
> the url wiki-url.html#:[permalink[1]] 
> In the wiki Open target this 
> can be dragged to bookmarks/favourites
>
> However I personally choose my tiddler names well enough when needed so 
> they need not change in future, and if I am publishing a link somewhere it 
> is to access specific content. the link has a purpose, and once someone has 
> the link the purpose is fixed in time and should always honour its original 
> share.
>
> A version of the above method where the link filter 
> is [has[permalink]last[]] will always link to the largest permalink value, 
> so one is sharing a link to the latest permalink tiddler or post.
>
> Another supportive trick is to hide the field from the editor with a 
> tiddler of the form $:/config/EditTemplateFields/Visibility/fieldname 
> eg $:/config/EditTemplateFields/Visibility/permalink with a value of hide
> thus once set you have to go out of your way to alter the permalink value, 
> that is its more permanent.
>
> Further developments (optional reading)
>
>- Since the addition of the unused title operator, it is possible 
>(more to the point easier) to use this to generate a unique and 
> incremented 
>tiddler title and serial number. 
>- Rather than shadow tiddlers I am using this not only to generate a 
>tiddler Serial Number (TSN) but a "ghost tiddler" that follows any tiddler 
>and provides a way to save metadata for any tiddler or field there in 
>(regardless of the title)
>- My only issues left are 
>   - Finding a way to generate/assign such TSN and Ghost tiddler in 
>   bulk.
>   - rebuild a parallel solution - system serial number, to assign a 
>   serial number to core and shadow tiddlers without touching them
>- Actually I have found you need only assign serial number where to 
>need them, say for these permalinks or compound tiddlers, that is with 
>subtiddlers that use the serial number for the parent rather than the 
> title 
>or a tag.
>
> Regards
> Tones
>
> On Thursday, 22 July 2021 at 06:50:01 UTC+10 springer wrote:
>
>> About obsolete permalinks: 
>>
>> Surely a variant of the relink plugin could help maintain bread-crumbs 
>> for obsolete links:
>>
>> Whenever relink does its thing, have it offer to create a 
>> dictionary-tiddler entry pairing old-name and new-name; then have a 
>> filter-condition ViewTemplate element show up at the bottom of old-name 
>> tiddlers, where the new-name tiddler is transcluded (or linked-to) -- 
>> perhaps pre-pending a note explaining that the old "Bombay" is now called 
>> "Mumbai"...
>>
>> At first, I was worried about the case where I change tiddler title from 
>> "Bombay" to "Mumbai" and then later generate a different one called 
>> "Bombay" -- but there, too, I might be interested in seeing

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[ludwa6]

Cool! the final step (i.e. cleanup) needed to flatten a Stream of nodes 
into a single tiddler, while preserving hierarchal presentation in readily 
portable form.  
I'll be using the heck out of this.
Nice job of scaffold-building, @Saq / @Jan / @Fred ; you guys rock!

/walt


On Thursday, July 22, 2021 at 2:58:02 PM UTC+1 saq.i...@gmail.com wrote:

>
> Also need to find an easy way to delete all the node-tiddlers rendered 
>> superfluous, once i flatten using your modal ; this is the one function of 
>> Jan's addon that i miss... 
>>
>> Delete the root tiddler the way you would delete any other tiddler. You 
> will be prompted to delete it's nodes as well.
>
>  
>

-- 
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/6d2c42b9-f03b-47f8-a224-1957520366cen%40googlegroups.com.

Re: [tw5] I broke the json pre-release :|

[springer]

Tones and Mario,

For public-facing projects, being able to name tiddlers with natural 
language expressions (including spaces) has been essential, and it seems 
much of the expanded power of fields in 5.2.0 will come from scanning for 
matches between field names and tiddler titles. 

(Emojis and such may seem trivial, but certain specialized unicode 
characters like Σ, plus expressions in two-byte languages like 字, are 
surely going to be leveraged by a significant user base as well.)

So, as much as it may seem logical to stick to CamelCase titles and 
a-z_special.string fieldnames for certain users, it seems the 
flexible-field-names horse is going to be galloping out of the barn as soon 
as the new version is available.

Might we figure out some way to test the compatibility of existing plugins 
(such as Shiraz) more systematically than by trial and error?

-Springer

On Thursday, July 22, 2021 at 12:24:46 AM UTC-4 TW Tones wrote:

> Mario,
>
> I am glad someone concurs. For me with my de facto standards and the new 
> freedom, if a field name looks like a tiddler title it possibly is.
>
> Do you think many ancient and / or unsupported plugins will break?,. if 
> they use fields even extensively the issue will only be if they are used 
> against new fieldname standards. And until now at least we tended to honour 
> any values if not fieldnames.
>
> I will be honest though few if any system tiddlers I create have spaces or 
> quotes of any kind. even tags are usually single text strings, and I do 
> think I will stick to this, as it simplifies code. but yes, use it when the 
> exception makes sense.
>
> I have not yet considered what we may achieve by having field names that 
> can be wikified into something else, but again I personally intend to 
> proceed with caution. Perhaps the documentation can give some advice to 
> this effect, for example currently the fieldname restrictions help us when 
> generating csv files and if field names (and values) contain spaces, or 
> commas and quotes this may no longer be true. The documentation should 
> continue to list the previous limited naming standards as well. 
>
> I must say I also have de facto naming standards for titles even although 
> they are quite flexible, in fact most that I code follow a simple and 
> limited range. I like to leave the flexibility for when its needed. The one 
> exception is when a title is also textual content like a sentence or 
> paragraph.
>
> Regards
> Tones
> On Thursday, 22 July 2021 at 13:56:18 UTC+10 PMario wrote:
>
>> On Thursday, July 22, 2021 at 3:24:54 AM UTC+2 TW Tones wrote:
>>  
>>
>>> However am I the only one who still intends to keep field names to a 
>>> defacto naming standard such as i-am-afield no caps or spaces? so It is 
>>> easy for me to tell field names apart from text and titles!
>>>
>>
>> No -- you are not.
>>  
>>
>>> Of course I look forward to naming fields using tiddler titles (and the 
>>> value a relationship type etc..). and to contain special prefixes or 
>>> suffixes such as "-link" or (link)  but as a rule I would like a little 
>>> structure and naming rules. 
>>>
>>
>> You wrote, you want to have tiddler titles as field names. So your 
>> field-rules have to be the same or a superset of your title rules. I would 
>> be surprised, if "no caps or spaces" is one of them. 
>>  
>>
>>> This always helps retain a degree of simplicity when managing lots of 
>>> complexity.
>>>
>>
>> Oh it will be funny, to deal with all the support requests here in the 
>> group, because some ancient and / or unsupported plugins will break. ... 
>> I'm not even sure, what my own plugins will do with "spaces" in field 
>> names. ...  I will have to check that. 
>>
>> 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/0dc65571-6786-41d3-a47d-f77ee5146b04n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Saq Imtiaz]

> Also need to find an easy way to delete all the node-tiddlers rendered 
> superfluous, once i flatten using your modal ; this is the one function of 
> Jan's addon that i miss... 
>
> Delete the root tiddler the way you would delete any other tiddler. You 
will be prompted to delete it's nodes as well.

 

-- 
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/77b1e8bc-ca6f-48fc-aed9-2ab1f3f0c97en%40googlegroups.com.

Re: [tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[Mohammad Rahmani]

On Thu, Jul 22, 2021 at 5:18 PM PMario  wrote:

> Hi
> I did create an issue:
> https://github.com/Jermolene/TiddlyWiki5/issues/5907
> -m
>

Thank you Mario! Yes 0.13.3 has tones of new features and bug fixes!




>
> On Thursday, July 22, 2021 at 2:39:05 PM UTC+2 PMario wrote:
>
>> Hi,
>> It seems {align} support started with KaTex 0.13.0 ... The version used
>> in TW is 0.12.0 which is about 1 year old.
>> So we will probably need to make an update.
>> -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/df1414dc-338b-4983-8d14-0cbc741f4608n%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/CAAV1gMCxvwW3JnnVGQ_3oZTGrjsLAeEb531bPAumvZLnCoifRQ%40mail.gmail.com.

Re: [tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[Atronoush Parsi]

@PMario Thank you for help and ticket on GitHub
Yes, please! Hope it gets updated for TW 5.2.0 release! I think TW 5.1.23
would not get the update

@Si - I did not know this I just looked the KaTex help page and try to
implement the examples

@Pak - Thank you! While align does not work with current TW+KaTex 0.12 but
amazingly aligned worked ;-)

Thank you all

On Thu, Jul 22, 2021 at 5:18 PM PMario  wrote:

> Hi
> I did create an issue:
> https://github.com/Jermolene/TiddlyWiki5/issues/5907
> -m
>
> On Thursday, July 22, 2021 at 2:39:05 PM UTC+2 PMario wrote:
>
>> Hi,
>> It seems {align} support started with KaTex 0.13.0 ... The version used
>> in TW is 0.12.0 which is about 1 year old.
>> So we will probably need to make an update.
>> -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/df1414dc-338b-4983-8d14-0cbc741f4608n%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/CAKHVXmpyz-dDGL02jh-GNVbj5YNrUP4%3DzixGn5E76XGcv3GXmQ%40mail.gmail.com.

[tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[PMario]

Hi 
I did create an issue: https://github.com/Jermolene/TiddlyWiki5/issues/5907
-m

On Thursday, July 22, 2021 at 2:39:05 PM UTC+2 PMario wrote:

> Hi,
> It seems {align} support started with KaTex 0.13.0 ... The version used in 
> TW is 0.12.0 which is about 1 year old. 
> So we will probably need to make an update.
> -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/df1414dc-338b-4983-8d14-0cbc741f4608n%40googlegroups.com.

[tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[Si]

@Atronoush

It's because {align} and {equation} were only added in Katex v0.13.0 
(https://github.com/KaTeX/KaTeX/releases?after=v0.13.4)

The current TiddlyWiki plugin is still on v0.10.0, and the pre-release is 
on v0.12.0. I would suggest adding an issue to github asking if the plugin 
can be updated to the latest version of Katex.

On Tuesday, 20 July 2021 at 15:58:58 UTC+1 Atronoush wrote:

> Testing in Tiddlywiki 5.1.23
>
> https://tiddlywiki.com/plugins/tiddlywiki/katex/
>
> Some example of KaTex:Supported Functions · KaTeX 
>  
>
> like
>
> \begin{align}
>a&=b+c \\
>d+e&=f
> \end{align} 
>
>
> return errors! Is there any setting I missed or Tiddlywiki does not 
> support these features?
>
> Mor example which do not work:
>
> $$
> \begin{equation}
> \begin{split}   a &=b+c\\
>   &=e+f
> \end{split}
> \end{equation} 
> $$
>
>
>
>
>

-- 
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/4d2c90d6-cbd0-463d-b25b-ff33c5ca6eb8n%40googlegroups.com.

[tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[PMario]

Hi,
It seems {align} support started with KaTex 0.13.0 ... The version used in 
TW is 0.12.0 which is about 1 year old. 
So we will probably need to make an update.
-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/a498401b-f74f-4412-923d-30b2b67badefn%40googlegroups.com.

[tw5] Re: tidders created this week

[Soren Bjornstad]

On Wednesday, July 21, 2021 at 9:58:33 PM UTC-5 TW Tones wrote:

> From the pre-release this feature should make it even simpler
>  New in: 5.2.0 Literal macro parameters are supported 
> . For example: 
> [].
>

Ooh, that's slick, looking forward to it!

-- 
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/3d4101b7-8352-4406-8004-479caae473c4n%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[ludwa6]

Yes, @Fred: just replicated your process, and got the same result 
-success!  Thanks for prompting me to try again :-)

Now i just have to remember to click the 1st button (yours), not the 2nd 
(Jan's)... 

Also need to find an easy way to delete all the node-tiddlers rendered 
superfluous, once i flatten using your modal ; this is the one function of 
Jan's addon that i miss... 

/walt

On Thursday, July 22, 2021 at 12:15:45 PM UTC+1 fred@gmail.com wrote:

> @Walt 
>
> Using TiddlyDesktop, I created a new TW (pre-release), imported Saq's 
> Streams  (latest) and relink 
> , the 
> 5 tiddlers from Jan's streams-to-text addon , 
> and my streams-fusion . 
>
> I experienced no issue; for tiddlers with stream nodes, two buttons appear 
> next to the add node button and both are functional. I am afraid I can't 
> replicate the issue you were experiencing yesterday.
> [image: image.png]
> [image: image.png]
>
>
> On Wed, 21 Jul 2021 at 17:02, Saq Imtiaz  wrote:
>
>> On Wednesday, July 21, 2021 at 10:38:28 PM UTC+2 Mark S. wrote:
>>
>>> So, you have to add manual config even though it's set up in the relink 
>>> plugin config?
>>
>>
>> Since your rename is happening outside of the Streams UI, yes. If you 
>> trigger a rename using the built in affordances, it is handled 
>> automatically if Relink is installed.  $:/config/RelinkOnRename is the 
>> default configuration tiddler which controls for both the core and relink 
>> what happens when renaming a tiddler via the edit template. It would be an 
>> overreach for Streams to change that behaviour that for users who rename 
>> outside of the Streams UI.
>>  
>>
>>> It might be helpful if this was mentioned in the installation tiddler. 
>>> Most people are going to assume that if they have the relink tiddler that 
>>> they're good to go.
>>
>>
>>  Have not had any reports of this being a problem since the very first 
>> Streams release. Contributions to the documentation are always welcome.
>>
>> -- 
>>
> You received this message because you are subscribed to a topic in the 
>> Google Groups "TiddlyWiki" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> tiddlywiki+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/tiddlywiki/dc3ac1af-c0d1-4b2c-9085-ca8682d427fdn%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/8c33f3ac-dec8-4357-bfdb-b708503926bfn%40googlegroups.com.

Re: [tw5] Re: NoteTaking in Streams - hierarchy-preserving flattening in wikitext

[Frédéric Demers]

@Walt

Using TiddlyDesktop, I created a new TW (pre-release), imported Saq's
Streams  (latest) and relink
, the 5
tiddlers from Jan's streams-to-text addon , and my
streams-fusion .

I experienced no issue; for tiddlers with stream nodes, two buttons appear
next to the add node button and both are functional. I am afraid I can't
replicate the issue you were experiencing yesterday.
[image: image.png]
[image: image.png]


On Wed, 21 Jul 2021 at 17:02, Saq Imtiaz  wrote:

> On Wednesday, July 21, 2021 at 10:38:28 PM UTC+2 Mark S. wrote:
>
>> So, you have to add manual config even though it's set up in the relink
>> plugin config?
>
>
> Since your rename is happening outside of the Streams UI, yes. If you
> trigger a rename using the built in affordances, it is handled
> automatically if Relink is installed.  $:/config/RelinkOnRename is the
> default configuration tiddler which controls for both the core and relink
> what happens when renaming a tiddler via the edit template. It would be an
> overreach for Streams to change that behaviour that for users who rename
> outside of the Streams UI.
>
>
>> It might be helpful if this was mentioned in the installation tiddler.
>> Most people are going to assume that if they have the relink tiddler that
>> they're good to go.
>
>
>  Have not had any reports of this being a problem since the very first
> Streams release. Contributions to the documentation are always welcome.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "TiddlyWiki" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> tiddlywiki+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/tiddlywiki/dc3ac1af-c0d1-4b2c-9085-ca8682d427fdn%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/CAAY2DnPZhYQRfhyUT5wqU50%2BNLbED2yj1FfmLTgD5SHQp34iSA%40mail.gmail.com.

[tw5] Re: Katex and TiddlyWiki: Some syntax does not work

[Pak]

My understanding is that in order for TW to parse an expression with katex, 
the expression needs to be inside $$ (or <$latex> widget). Otherwise the 
expression is treated as a wikitext/html.  That might explain why 
\begin{align} does not work - it's not inside $$ so TW does not know to 
parse this as a LaTeX command.

If you want align environment, you can use
$$
\begin{aligned}
   a&=b+c \\
   d+e&=f
\end{aligned}
$$
On Tuesday, July 20, 2021 at 9:58:58 PM UTC+7 Atronoush wrote:

> Testing in Tiddlywiki 5.1.23
>
> https://tiddlywiki.com/plugins/tiddlywiki/katex/
>
> Some example of KaTex:Supported Functions · KaTeX 
>  
>
> like
>
> \begin{align}
>a&=b+c \\
>d+e&=f
> \end{align} 
>
>
> return errors! Is there any setting I missed or Tiddlywiki does not 
> support these features?
>
> Mor example which do not work:
>
> $$
> \begin{equation}
> \begin{split}   a &=b+c\\
>   &=e+f
> \end{split}
> \end{equation} 
> $$
>
>
>
>
>

-- 
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/c2b3d259-1a7d-42a6-b029-8f84d470ffd1n%40googlegroups.com.

[tw5] Re: Two problems with macro: displaying and refreshing

[Misterel85]

Ciao Tones,
An interesting guess you've tried to make here. Well, you could have added 
the similarity of the name I chose here with the 'massif de l'Esterel', a 
mountain range between Cannes and Saint-Tropez!

Well, that alias is closer to English than French, actually. It dates back 
to my year as a French assistant in Scotland. Some pupils at the boarding 
house didn't bother call the tutors by their full name, so they used the 
initial of the family name: 'Mr. T.', 'Mr. S.' or, in my case, 'Mr. L.'...

I'm sorry to disappoint you but I'm from the West of France. I live near 
Nantes, and my parents' house was very close to 'Le Puy du Fou' a renowned 
sound-and-light show about the history of the area. The French dialect I 
would use is probably closer to Charlie Veniot's Acadian French than to 
Occitan, I'm afraid. I enjoyed reading some words and phrases in his 'Le 
P'tit Aurèle', and could understand most of them at first glance, since 
were also used by my the elders in my family.

I do miss travelling as well, although I don't know France that much. I'm 
more used to visiting English-speaking countries.

Stéphane L.

Le mercredi 21 juillet 2021 à 03:39:58 UTC+2, TW Tones a écrit :

> Thanks for sharing your result back here Misterel, it is great community 
> participation.
>
> Yup, TiddlyWiki is so awesome.
>
> With the name Misterel, makes me think of thew Mistrals and "Pas de" in 
> your code I imagine you may be in the south of France? We have friends in a 
> place called Castries not far from Montpelier, it was there I saw the 
> result of the Mistrals (winds) in their back yard with every tree leaning 
> away from the wind. Strangely whilst their house was a modern Spanish 
> style, their pool and barbeque area was quite similar to nice homes here in 
> Australia.
>
> We miss France terribly, and can't wait to visit again. My partner 
> Isabelle's mother remains in Paris and we have family all over 
> France/Portugal.
>
> Tones/Tony
>
> On Wednesday, 21 July 2021 at 04:56:03 UTC+10 Misterel85 wrote:
>
>> Hi everyone,
>>
>> With Springer's help and and bit of googling around, I finally found a 
>> (basic) working solution. Yay!
>> It is much simpler to use a ViewTemplate instead of a macro and it should 
>> satisfy most of my needs.
>>
>> Should it be useful to anybody, here is the code I used in the 
>> ViewTemplate to replace the macro:
>>
>> ```
>> <$list 
>> filter="[all[current]field:tiddler-type[exercice]field:displaysource[yes]]">
>> <$set name="fieldCount" 
>> filter="[all[current]fields[]prefix[ref_]count[]]">
>> <$text text={{{ [match[0]then[Pas de ]else] }}} />
>> <$text text={{{ [!match[1]then[sources :]else[source :]]  }}} 
>> />
>> 
>> <$list filter="[all[current]fields[]prefix[ref_]sort[title]]" 
>> variable="fieldName">
>> @@color:grey; 
>> 
>> <$transclude field=<>/>
>> @@
>> 
>> 
>> 
>> ```
>> I can't believe how great and versatile TiddlyWiki is!!
>>
>> Regards
>>
>>
>> Le mardi 20 juillet 2021 à 18:35:59 UTC+2, Misterel85 a écrit :
>>
>>> Springer,
>>> Thanks a lot for taking the time to reply and for your help.
>>>
>>> You're exactly right: I'd like my macro to count (and then display one 
>>> summary line for) each of the fields that start with ref_ in every tiddler 
>>> in the story river.
>>>
>>> I have tried your solution to add `all[current]` in my macro but 
>>> unfortunately it doesn't work.
>>> Actually because the macro is in its own tiddler, I think `all[current]` 
>>> tries to find the ref_ fields in the macro's tiddler. But I may be wrong.
>>>
>>> Grok TiddlyWiki is a great tool to learn, but I haven't finished reading 
>>> it, and it needs time to figure out all the intricacies of (TW) programming 
>>> when your coding knowledge amounts to next to nothing.
>>>
>>> Regards
>>>
>>>
>>> Le mardi 20 juillet 2021 à 17:32:35 UTC+2, springer a écrit :
>>>
 Misterel,

 I am *not* the expert; others could probably write the code you need in 
 60 seconds. But since nobody else has answered, and understanding your 
 task 
 and its problems demands some time and attention, I'll offer one nudge to 
 start...

 It seems you want your macro to count (and then display one summary 
 line for) each of the CURRENT tiddler's fields that start with ref_ -- Is 
 that correct?

 Instead, your macro is counting (and then displaying one summary line 
 for) every field in your whole wiki that begins with ref_

 Try pasting your code (with the variable filled in) and this alternate 
 code, into your Exercice1 tiddler. Your code yields 5, because the whole 
 project had five ref_ fields; but beginning your filter with 
 [all[current] gets you the number you want.

 First segment of your existing macro's code (specifying the prefix):
 <$set name="fieldCount" filter="[fields[]prefix[ref_]count[]]">
 <$text text={{{ [match[0]then[Pas de ]else] }}} 
 />
 <$text text={{{ [!match[1]then[sources :