Am Mittwoch, 23. Oktober 2013 17:50:04 UTC+2 schrieb PMario: > > > We did discuss this topic yesterday at the hangout. see: > http://www.youtube.com/watch?feature=player_detailpage&v=LEFadJ6Ls2Y#t=2626 >
So if I understood correctly, using ~ as an escape character for the next "element" could be an option. If so, don't forget to make ~~ render as just one ~. I also took a look at the code today and I found that the ~ at the moment is coded into the parser for the links. If it's generalized, I think this would be much "cooler" as the parsers don't need to know about the ~ at all. My approach to this would be like this: Every parser gets an additional boolean parameter called "escaped". The parser always matches the same way regardless of what "escaped"'s value is. When it comes to returning its result, and "escaped" is "true", always a text object with the text being just what it matched is returned. If "escaped" is false (or missing?) the parser returns what it is already returning now. So before calling the parsers, a check needs to be done, whether or not we have a single ~. If so, escaped will be set to true. Does this sound reasonable? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/groups/opt_out.
