I totally understand, that is in part why I mentioned @jeremyruston the “code controller, and whisperer” .
One persons “argument over lapping” is another persons “sophisticated parameter handling”.
- I think this fair. Actually you may be in a position to write a short guide, telling people how to wright code that is relink aware. Why leave it in the lap of the gods?, let god himself write the commandments
You know relink is so good, I often ask myself will it handle this change or that and it just does, it is successful so often, I get a little lackadaisical.
- I do check the details when writing something I expect to rename, especially recently, when playing games with namespaces (optional reading only Expanding the is system namespace) and thus I do make RELINK a prerequisite.
- Another time I check the documentation is when I am writing something where I want to ensure referential integrity beyond normal tiddlywiki behaviour. Relink has always being there to allow me to do such things.
Actually, I possibly only depend on and can’t live without the first 20% of relinks functionality, all the rest is just a bonus, and due to my own ignorance I check if it’s going to work for me in special cases, when the need arises. Further If I found something that did not work, or code I wrote poorly, all I do is use other tiddlywiki refactoring methods.
- The point being, I appreciate you trying to make RELINK all things for all people and you get very, very close but it is a lot to expect of yourself.
/5