Mat is that matching the "</$" cases? ...
In regex in TW "/" is not an issue. It does not need escaping. It's only an
issue in raw JavaScript.
Just FYI my take on your issue is ...
*(/>|</\$)+*
notes: the "\" before $ suppresses the special meaning of $ in regex. The
"+" at the end forces the alternation to repeat if necessary (I.e. makes it
or/and).
The pattern assumes there would be no spaces between ">" and "<".
Best wishes
TT
On Wednesday, 1 July 2020 13:20:18 UTC+2, Mat wrote:
>
> Solved it. To my surprise, no escaperegexp is needed, i.e:
>
> <$set name=closures filter="[{!!widgetclosure}]"
> {{{ mystring +[regexp<closures>] }}}
>
> ...is enough when widgetclosure: />|</$
>
> No need to escape e.g the / characters. Convenient (...but how can this
> possibly work?)
>
> <:-)
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/d68d0e16-db16-422f-bb2a-3a15db21c565o%40googlegroups.com.
