> Repairing this behavior is essentially a two-line modification to the > handler function: <snip>
That makes sense, and is a useful modification. As you say, a similar modification would need to be made to most of the formatters. > Currently the config.formatters are loose to trigger a match and more > strict in applying the markup. That's right. I may say that not many people have got as far as you in plumbing the depths of this code. I paid a lot of attention to piggybacking on the (relatively) good performance of regular expressions. > This would have the effect of making unmatched markup more obvious in > the output (as the match characters are displayed). > It also allows users to use characters that coincidentally look like > markup but don't strictly follow it (using only one-half of an > enclosed markup). > I'm a bit fuzzy on it's application in some forms of markup. For > example: if you don't close a bold tag '', then all text after those > two characters are one big bold block. Is this intentionally lax with > closing the tags? That seemed like the correct behaviour; at least the visual effect was obvious, helping debug such mistakes. Best wishes Jeremy > > Comments are encouraged. > -- > David Young > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/tiddlywikidev?hl=en. > > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
