Right. Its much worse for computer illiterate users like me who have no clear idea what is right and wrong in the lingo format.
I just assume that live feedback on coding errors would bloat TW beyond reasons for it. Josiah On Friday, 14 December 2018 19:48:01 UTC+1, joearms wrote: > > I just spent a good half an hour scratching my head. > > I made the following error > > I wrote: `<<list-links filter:"[Prefix[How]]">>` > > Instead of: > > `<<list-links filter:"[prefix[How]]">>` > > (I know it should be a small "p" and not a big "P" - but errors like this > (silent errors) > are extremely difficult to spot. I call errors like this `quiet errors`. > > I have no idea how the filter mechanisms are implemented but it would be > extremely helpful if all programming errors if they can be detected be > converted into "noisy errors" > > Noisy errors stop the program execution with a huge red error text telling > you what went wrong. Quiet errors just swallow up the error and say nothing. > > As a general design principle, I believe that all plugins etc should > generate noisy errors if they detect an error condition. > > Cheers > > /Joe > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/d3c26171-3e5d-4e9a-a013-870dbe7ad5c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
