On Monday, August 14, 2017 at 11:49:00 AM UTC+2, @TiddlyTweeter wrote: > > Could yours (its just a single macro, right, not a plugin with > dependencies?) be re-factored to accept ANY filter through an input field? >
Sure, ... _but_ it would be very destructive and error prone. eg: If there is a typo. - Let's imagine a filter like: [prefix[$:/temp]] - it will also delete $:/temptation - which may not be intended. ... Do you see the the missing char in the filter variable? .. and this example contains an obvious problem. Filters can have side-effects, that are much harder to spot. I know, that's a user problem, if s/he creates a filter that dosn't do what is intended, or if a filter has unintended side-effects ... I think the plugin contains enough info, that users can create their own variations of the macro, that work for their specific usecase. I personally don't want to be responsible, if *my plugin* deletes stuff that the user wanted to keep. So everyone, which wants to be responsible can jump in here. have fun! mario -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to email@example.com. 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/47a7c4d6-c123-409f-baa5-aabdda0021d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.