Hi Jim

> because frankly I have spent probably somewhere between 20 and 30 hours
trying to figure this out over the course of two weeks

Ouch! I'm sorry for the frustration that must have caused, and I admire
your dedication in sticking with it. It's good that it was instructive,
anyhow. I'm all too familiar with the experience of bashing ones head
against a coding wall, and then having the further pain of kicking oneself
once the answer has been revealed.

I'm glad you'll be making progress again,

Best wishes

Jeremy.




On Sun, Dec 7, 2014 at 8:13 PM, Jim Lehmer <[email protected]> wrote:

> That, in fact, did work. Thanks.
>
> I support your recent effort to spend December doing more documentation,
> because frankly I have spent probably somewhere between 20 and 30 hours
> trying to figure this out over the course of two weeks, including profiling
> code, reading code, doing code searches, etc. I consider myself reasonably
> technical (programmer since 1986, architect since 1996) and I don't know
> that I would have *ever *figured that out (I was absolutely *sure *it was
> because of the *tv_wikilinks *macro after reading the code that uses it,
> and had spent the last few hours trying to hunt down where it was getting
> set to "no" with obviously no success, since that wasn't the issue).
>
> I like TW, I am impressed with it and want to use it, but I know 99% of
> people would simply have stopped about 10 days ago. I just happen to like a
> good mystery. :)
>
> Thanks, again.
>
> On Sunday, December 7, 2014 1:55:32 PM UTC-6, Jeremy Ruston wrote:
>>
>> Hi Jim
>>
>> My apologies for the late reply.
>>
>> When static templates are rendered, they are saved as plain text. That's
>> why the raw html in the template is enclosed in backticks, to force it to
>> be treated as text rather than interpreted as HTML when it is parsed.
>>
>> The mechanism for  including content so that the HTML tags are rendered
>> is to use <$view field="text" format="htmlwikified" />. The easiest way to
>> do this is to put your content into a tiddler and transclude it the
>> template "$:/core/templates/html-tiddler". For example:
>>
>> {{$:/static/toc||$:/core/templates/html-tiddler}}
>>
>> Where $:/static/toc contains your invocation of the <<toc>> macro.
>>
>> Let me know how it goes,
>>
>> Best wishes
>>
>> Jeremy.
>>
>>
>>
>>
>>
>> On Sun, Dec 7, 2014 at 6:41 PM, Jim Lehmer <[email protected]> wrote:
>>
>>> I replaced the toc macro with a single link widget and it has the same
>>> behavior, i.e., it outputs the text contained in the widget, but doesn't
>>> wrap it in an anchor tag.
>>>
>>> Reading in the documentation for the link widget, I note this:
>>>
>>> tv-wikilinks
>>>>
>>>> Links are suppressed if the macro tv-wikilinks evaluates to the string
>>>> no. For example:
>>>>
>>>> \define tv-wikilinks() no
>>>>
>>>>
>>> However, the static.tiddler.html tidder does not define that macro one
>>> way or another, and even trying to redefine it with a value of yes doesn't
>>> change behavior. I have searched through the npm package and found all
>>> places that is set to no, but none seem relevant here.
>>>
>>
>>
>>
>> --
>> Jeremy Ruston
>> mailto:[email protected]
>>
>


-- 
Jeremy Ruston
mailto:[email protected]

-- 
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 http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to