The problem is that a large number of macros rely on the current behaviour, and that a fix would break these macros.
The correct fix would be to remove the call to readMacroParams() in invokeMacro() and then have any macros parse their parameters themselves. But as I said, this will break a large number of plugins. Martin 2009/10/25 Tobias - http://tbGTD.tiddlyspot.com <[email protected]>: > > Hi everyone, > > I am looking for a solution/method to get around this behaviour where > macros are executed twice. Searching trac I sadly find this issue to > be a wontfix http://dev.tiddlywiki.org/ticket/1035 > > Is there anyone here who knows how to fix it? I personally would love > to see this annoying behaviour to be a thing of the past, even if that > means that I have to mod every single defective plugin myself. > > Plugins are not set in stone, if the platform (tiddlywiki) moves on, > because at some point it didn't quite go down the right road, so must > its applications (plugins & other bits of code) or they will fall > behind. > > The tiddler macro turns out to do a great job at transclusions! And > that is why I think this idempotency issue is restricting its > usability way too much, like 'you better not wikify'... > > Tobias. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
