Please forget my configurability suggestion, it was a misunderstanding on my part. (..but, in cased the post at 11:11 was missed, I do think that "zoOM" is more natural than 'zoOM ).
Here are some other thoughts: 1) How would you linkify a common multiple word root such as snow board (snow boarding, snow boarder, snow boarders etc)? 2) Regarding ^ or 0!, if I understand it correctly, the purpose is to first locally disable the CamelCase linking feature and apply linkify instead. If LinkifyPlugin is used, is there actually any need for the CC linking feature? Please let me explain: I use CC almost exclusively for one thing, ie. choosing a tiddler name that AVOIDS forcing me to use [[ ]] later on. That, actually, is pretty much it. If I didn't have to take this into consideration, I'd gladly skip it. There is one more common *occurence* of the CC which is an incidental (accidental?) one - namely when you write a text and only later realize that "ah, darn, that was apparently a CC word... gotto add ~". That is CORRECTING a mistake, which is at par with AVOIDING, if now worse. ...my point? Well, just maybe it makes sense with an option (a checkbox?) in LInkifyPlugin to turn off CC. If links are automatically created with linkify, particularly for/to tiddler names, then I see little point with the whole CC issue. Obviously(?) anyone can still write things in CC format and if Linkify is later disabled then I presume the CC feature would be activated again. <:-) On Apr 12, 6:44 pm, Tobias Beer <[email protected]> wrote: > Hello twgrp and PMario, > > The current discussion might be a bit misleading in that I started by using > the term "prefix" and now you are talking about suffixes too. > > In fact, these characters are rather meta characters, switches or flags. > > 1) They could be configurable since they (currently) do not end up in the > regex that is used for matching. BUT, I agree with Mario that for > readability's sake alone this should not be pursued. I believe that it is > fairly safe to expect people not to use characters like ^ ' * or ~ at the > beginning or end of either their tiddler titles or the text they want to > match. If one out of a Million should do this... well, bummer. Perhaps I > will allow \\ to escape a meta character in order to use it in its literal > sense. > > 2) You are right, Mario. The ^wordroot nomenclature is rather misleading. I > will therefore change it as you suggest to wordroot* which sure is a lot > more natural. > > Thus, I would currently vote to change the meta characters like so: > > ^PrependToFormattersArray > -> instead of the ugly "prefix" 0! > > 'MatchLETTERSasis > -> a single quote would trigger matching lower and uppercase letters > exactly as defined > > config* > -> the new wildcard at the end of the word instead of the beginning > > ~DoNotLinkify > -> to not linkify the first term but only define it as the tiddler to which > all other terms linkify ...separated by | > > Keep in mind that - at the moment - the wildcard * is only intended to > serve for word endings. > It currently is not intended to be used as {wild*card} or {*card} or even > {*middle*}. > I might check as to how hard it would be to allow it both at the beginning > or at the end of a term. > > Eventually, I don't think that these metacharacters should cover the full > range of what RegEx has in store, because *no one* will want to use that. > > Perhaps, I can imagine another pair of metacharacters like this... > > (any regex you want to be matched) > > Thus, any term wrapped in parentheses is evaluated as a RegEx. However, I > am not sure that there will be many people that know how to make use of > that or even want to in the context of LinkifyPlugin. > > Cheers, Tobias. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
