Hello Josiah, That is correct. I am thinking how I can find another solution to this. I submitted a request to GitHub asking for addition of replace (e.g searchreplace) to the new string operation filter. I am not sure if Jeremy accept this.
--Mohammad On Tuesday, February 26, 2019 at 11:14:39 PM UTC+3:30, @TiddlyTweeter wrote: > > As far as I can see the "splitter" is fully consumed if there is no > non-whitespace string between intervening split points. > > So string: "c, d, , ,f " splitting on "," consumes the splits between d > and f? In some ways it's understandable to dump null values. But it is > problematic in the current case. And its problematic more generally for > arrays where you need to preserve null entries? > > Just amateur thoughts > Josiah > > On Tuesday, 26 February 2019 15:41:31 UTC+1, Mohammad wrote: >> >> Hello Josiah! >> I think it is a bug in split operator. Test this on >> >> <$vars x="this at at best"> >> <$list filter="[<x>split[at]]"> >> >> </$list> >> </$vars> >> >> Split operator cannot distinguish the repeated word! >> >> Hope Jeremy have a look at it! >> >> --Mohammad >> >> >> -- 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/65cce8c5-b627-4d4f-ab8b-13215512916e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
