Hi Diego, Thx for the reminder. ... I'm very reluctant about hardcoding ?t, ?c, ?s ... What if existing users have valid links that look that way. ... So it would be needed to make a configuration for exceptions. ...
I did think about it. ... If the uni-link parser sees: [[alias|?]] it uses a macro call like this <<aka alias <https://wikilabs.github.io/editions/uni-link/#%24%3A%2Fplugins%2Fwikilabs%2Funi-link%2Faka-macros>>> The macro code for ?t, ?c and so on would look completely different. ... So what if ?t would call <<t alias>> and ?c would call <<c alias>> ... So it would be possible to define ?x which would call <<x alias>> I think this has a lot of potential, since the user could have as many alias representations as needed. There is some potential for mis-use and heavy performance problems, if misused, ... but I like the idea. What I don't like is backlinking this stuff, which will be needed. eg: Show me all alias links, that display with ?c ... and so on. The main problem is, that the more stuff we can do, the less likely it will become a "core" element. What do you think? -m -- 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/9f9b5dac-79b2-4b66-8c36-44de64dbe827%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
