PMario wrote > If it is configurable, it will cause different types of configuration > tiddlers, which will be incompatible. Imo this limits the "global" > usability of the plugin,
Could you please elaborate a little here. Why would defining the suffixes in the LinkifyConfig cause different types of configuration tiddlers? (Or do you mean between different users? Having only English suffixes literally limits the global usefulnes of it). An idea would perhaps be a hard coded standard set of suffixes, as already implementetd, but allowing the user to manually add additionall ones. Maybe this would not "limit the global usability" as you put it, or? <:-) On Apr 12, 4:59 pm, PMario <[email protected]> wrote: > On Apr 12, 11:11 am, twgrp <[email protected]> wrote:> For suffixes (that > is one GREAT feature, btw) it'd be more natural > > with the ^ in the end of the word, were all suffixes are added. > > And if it could be a * instead of ^ it would again be more natural > > although one may mistakenly assume it would include every possible > > ending... unless (yet another suggestion): > > I'd +1 this > > As I saw ^this the first time, I thought it means: find "this at the > start of the line", which is the meaning if used within a regExp. > > ===>How about letting the user define the "Suffixes" in LinkifyConfig? > >This is very much desired for non-English users or the suffix feature > >is lost. This would also make that * very natural (the user has > >defined everything it covers). > > -1 > > If it is configurable, it will cause different types of configuration > tiddlers, which will be incompatible. Imo this limits the "global" > usability of the plugin, > > -m -- 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.
