Thanks Jeremy & everyone else for the replies.

I did face an issue while working on Documentation, specifically for 
addressing Github Issue #3726 
<https://github.com/Jermolene/TiddlyWiki5/issues/3726> for tiddler: Using 
Stylesheets <https://tiddlywiki.com/#Using%20Stylesheets> 

It took me a long time to figure out why *<<.tag $:/tags/Stylesheet>>* was 
giving a link - instead of displaying like all other normal tags used in 
Documentation. I thought my modifications to the Documentation Macros was 
faulty. I finally understood how it was happening after some discussion in 
Google Groups: Does <<__...__>> make $...$ obsolete in macro definitions? 
<https://groups.google.com/forum/#!msg/tiddlywiki/QzvZD9GGTbg/Z9qxht5_BgAJ> 
followed by quite some experimentation on my own. It took many more hours 
than I wanted to sort out the issue.

Once I figured it out, I wanted to understand the rationale behind this. It 
is also useful for any Documentation writer to know the background when:

   1. We get around to doing the documentation for the: \rules Pragma 
   <https://tiddlywiki.com/#Pragma>
   2. We perhaps make a small mention of this default behaviour in tiddler: 
   SystemTiddlers <https://tiddlywiki.com/#SystemTiddlers> 
   
The reason given on GitHub issue #1103 
<https://github.com/Jermolene/TiddlyWiki5/issues/1103#issuecomment-64121465>  
that it elegantly solves the problem of writing *$:/tags/ViewTemplate* 
where the *ViewTemplate* portion would get Wikified (with CamelCase turned 
on) - is an explanation that makes good sense. A downside I can see is that 
all those references to tiddlers that don't exist show up in the Missing 
Tiddlers list.

Also I think that in the Documentation on tiddlywiki.com we should try and 
avoid such links to missing tiddlers that we have no intention of making. 
It is confusing to readers of the website, and gives an impression that the 
site has lots of broken links and unfinished documentation. I know I have 
felt that way for most of the first 2 years of reading documentation before 
I understood why the links were missing. During that time, I felt that the 
Documentation was very incomplete even though now I know it isn't.

I think it may be useful to re-visit the GitHub PR #2844 : Improve global 
"wikilink" parser disabling 
<https://github.com/Jermolene/TiddlyWiki5/pull/2844#issuecomment-312029335> 
where you wrote:

Generally, I'm thinking that new users tend to be confused by CamelCase 
> automatic linking, to the degree that we should perhaps consider disabling 
> it by default
>

Though CamelCase was useful many many years back, and then for a long time 
it was quaint, I believe it is no longer either of those to the present 
generation. It may be prudent to consider turning off both *CamelCase* and 
the *syslink* parser rule for both tiddlywiki.com and empty.html

The irritation of *$:/tags/ViewTemplate* where the *ViewTemplate* portion 
will get Wikified is easily solved for those that face the issue, by 
enabling the *syslink* parser rule on their own TiddlyWiki.

If PR #2844 is implemented and a general automated clean up of ~CamelCase 
and making [[CamelCase]] is done, and *syslink* turned off, I would be 
willing to spend some time helping to find stray cases that need fixing.

Thanks for your patience.

Regards.

On Monday, February 11, 2019 at 10:54:27 PM UTC+7, Jeremy Ruston wrote:
>
> Hi SS
>
> Autolinking of system tiddler titles was proposed and implemented by 
> Tobias Beer back in 2015:
>
> https://github.com/Jermolene/TiddlyWiki5/issues/1103
>
> I think that rationale was roughly the inverse of your question: why would 
> one want to refer to a system tiddler title without making it a link.
>
> I'm assuming though that you've run into some situation where system 
> tiddler linking causes a problem or confusion?
>
> Best wishes
>
> Jeremy
>
> --
> Jeremy Ruston
> [email protected] <javascript:>
> https://jermolene.com
>
> On 11 Feb 2019, at 11:05, S. S. <[email protected] <javascript:>> wrote:
>
> In the TiddlyWiki on tiddlywiki.com & in empty.html - the parser rule for 
> *syslink* is turned on by default. It can be seen at: Control Panel > 
> Info > Advanced > Parsing
>
> With syslink enabled, any text resembling a system tiddler name ( *$:/.* 
> ) gets turned into a link, I imagine in a similar way to CamelCase becoming 
> a link.
>
> I cannot see any practical use of this behaviour helping in any way for 
> either the tiddlywiki.com website, or a general user of TiddlyWiki. It 
> may also be confusing for users as there is no documentation mentioning 
> this effect - but even if there was, once a user would become aware of what 
> was happening and want to deal with the effect, it would be very difficult 
> to know what to search for to find an answer.
>
> Was there some particular reason that led to this being on by default, and 
> what would be the ramifications if it was switched off by default?
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "TiddlyWikiDev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> To post to this group, send email to [email protected] 
> <javascript:>.
> Visit this group at https://groups.google.com/group/tiddlywikidev.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/tiddlywikidev/1d5c50e7-8bbc-4438-8c16-3f954817a1bb%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/tiddlywikidev/1d5c50e7-8bbc-4438-8c16-3f954817a1bb%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" 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/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/2e7fac8f-6857-4198-81cd-d8a4c7cf19e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to