As maybe only a few might be aware, I have been proposing 
<https://github.com/Jermolene/TiddlyWiki5/issues/3624> that macros forming 
a part of TiddlyWiki's core that deal with the *caption* field should not 
break down when encountering an empty *caption* field. The main ones that 
do break down, and which I feel would be exasperating for normal users of 
TiddlyWiki, are the Table of Content *toc* macros and the *list-links* 
macro.

Well as part of trying to put forward a convincing case, I have tried many 
variations of fixing the toc-caption macro that resides in 
$:/core/macros/toc <https://tiddlywiki.com/#%24%3A%2Fcore%2Fmacros%2Ftoc>

My latest endeavour is shown in this post: 
https://github.com/Jermolene/TiddlyWiki5/issues/3624#issuecomment-466652926
I feel it finally passes all the requirements needed. Now the main hurdle 
left is a decision on if this change is the wanted default behaviour.

While looking at that proposal, I started wondering why something like 
*tiddler=<<currentTiddler>>* did not break down when a *Title* name 
contained text that would normally be *Wikified*.

<$set name="display" tiddler=<<currentTiddler>> field="caption">

By experience I know that a WikiText macro call: <<currentTiddler>>  : 
wikifies the variable, but within this widget, used as the value of a 
attribute, it does not *Wikify*.

So I made a tiddler to see what things looks like:

*Tiddler:*
title : Tiddler 10^^2^^
caption : 10^^2^^

`display` variable has been set using:

```
<$set name="display-caption" tiddler=<<currentTiddler>> field="caption">
```
`caption` field is: <pre><$view field=caption/></pre>
<hr>
<$set name="display-caption" tiddler=<<currentTiddler>> field="caption">

`<$view field=title/>`= <$view field=title/>

`<$text text=<<currentTiddler>>/>`= <$text text=<<currentTiddler>>/>

`<<currentTiddler>>`= <<currentTiddler>>

`<<storyTiddler>>`= <<storyTiddler>>

`<<display-caption>>`= <<display-caption>>

`<$macrocall $name="currentTiddler"/>`= <$macrocall $name="currentTiddler"/>

`<$macrocall $name="currentTiddler" $type="text/plain" $output="text/plain"
/>`= <$macrocall $name="currentTiddler" $type="text/plain" 
$output="text/plain"/>

`<$macrocall $name="currentTiddler" $type="text/plain" $output=
"text/vnd.tiddlywiki"/>`= <$macrocall $name="currentTiddler" 
$type="text/plain" $output="text/vnd.tiddlywiki"/>

`<$macrocall $name="currentTiddler" $type="text/plain"/>`= <$macrocall 
$name="currentTiddler" $type="text/plain"/>

`<$macrocall $name="currentTiddler" $type="text/html"/>`= <$macrocall 
$name="currentTiddler" $type="text/html"/>

The last two have HTML:

```
<pre><code>Tiddler 10^^2^^</code></pre>

<iframe src="data:text/html;charset=utf-8,Tiddler%2010%5E%5E2%5E%5E" sandbox
=""></iframe>

```
</$set>



Some of the results are quite interesting.

Another simple example is:

Tiddler:
title: Tiddler ^^11^^
<$link to=<<currentTiddler>>>{{!!title}}</$link>

The first "Wikitext" - <<currentTiddler>> - does *not* get Wikified because 
it is *not* being used in Wikitext.
The second "Wikitext" - {{!!title}} - does get Wikified beause it is in an 
area of Wikitext.

So, would it be correct to say that, in general when a macro or other 
Wikitext is used as the value of an attribute of a widget, that is NOT a 
case of it being used within Wikitext - so it is not Wikified?

And then, the *$wikify* widget is the one exception, as the widget can and 
does Wikify the value of its *text* attribute?

Note: Tiddler attached







-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywiki.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/9a8ccdb6-cf03-4953-bfa8-3a078334d7b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: Tiddler 10^^2^^.tid
Description: Binary data

Reply via email to