On Thursday, 10 January 2019 11:15:25 UTC+1, TonyM wrote: > > Joe, > > Newlines in filters do not work, however if you passed fieldname="value" > pairs to the create new tiddler action you could use newlines. That is do > not use the triple curly braces. You may need more set widgets, but it > would read better. >
Precisely - I have discovered this. BUT The documentation says whitespace IS permitted https://tiddlywiki.com/#Filter%20Whitespace:%5B%5BFilter%20Whitespace%5D%5D%20%5B%5Bsubfilter%20Operator%20(Examples)%5D%5D And I believed it, (aside) since no working program would have used linefeeds adding them now should not break backwards compatibility, but I'm no expert here (/aside) Now this not what the code does (which I have discovered through experimentation) So either: 1) the code is correct - and the documentation is buggy OR 2) the documentation is correct and the code is buggy OR 3) both are incorrect As a point of principle I strongly believe 1) - why? - because the TW is a mature program. Beginners (like me) read the documentation and believe it. If I write according to the documentation it is my expectation that it should work according to the documentation. Exactly this happened in the development of Erlang. The code and documentation differed. In the beginning, code won and documentation lagged behind. Later, when Erlang was mature I wrote a book and decided "the book is definitive" - if the behaviour of the system differs from the book then the behaviour is wrong and it's a bug in the code. I would like to see this change happening in the TW - remember a lot of potential users sill silently give up when they fail to do something and will not shout their heads off like me. It basically boils down to "who do you believe" the code or the documentation. In a new system it's the code - in a mature system it's the documentation. Getting both to agree is a long and painful process - so I don't underestimate the difficulty. Been there done that - wrote the code - wrote the book :-) Cheers /Joe > Alternatively you could define the filter in a (global) macro and place it > in the create tiddler using the subfilter operator, after all you may want > to use it more than once. > > You could even move set widgets to macros if they define reusable > variables, this would provide a tiddler of sharable settings and much > simpler new tiddler code. > > That should give you multiple avenues to write readable self documenting > code. > > I assume you are wrapping this in a trigger widget such as a button? > > Regards > Tony > > -- 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/ed238c30-a1a6-4c86-97cc-6e066cf8313e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
