freelinks and relink??

[HC Haase]

The freelink plugin is realy great and it has been a wish of mine for a long time.

However, if you use the great Relink plugin, and rely on all links to be renamed if you edit the title of a tiddler, alas there is a shortcoming. The freelink link is not a hard link and will not be edited by Relink.

I wonder if re-link could support the freelink "links" somehow??

[Flibbles]

Sorry, I completely missed this. I don't normally sift through this group unless I want something.

This integration actually wouldn't be that hard. I might make it in a week or so. Currently, I'm really burned out after having added markdown support.

[springer]

HC (and all), here's a place for that adage: "That's not a bug, it's a feature!" 

Getting updated by relink is precisely what many of us would *not* want "freelinks" to try to do. Freelinks are "soft" links, floating "above" tiddler text; though the connection can be recognized, the tiddler text itself sits solidly on the ground, unaffected by the presence of the link.

In my academic use case, I have a reason to prefer it that way. There's plenty of tiddler text *not* authored by me. It should stay just as it is -- relatively "hard" text. The beauty of freelinks is how various implicit connections (to concepts I'm discussing) *jump out* of that existing text. But if I change the title of one of my concept-discussion tiddlers, I most certainly would not want my source texts to get overwritten!

Granted, I might be happy for the *option* to scan and select some places where my title-edit should reverberate through some other tiddlers. But if variants of freelinks and relink were ever to "shake hands" in this way, this must be a clearly marked and optional development, or it will break much of what makes freelinks great, for users like myself.

-Springer

On Monday, April 20, 2020 at 5:49:31 AM UTC-4, HC Haase wrote:

[Flibbles]

The way I'd do it is to create a child-plugin which users can optionally install. I just finished creating very nifty child-plugin support for Relink in order to optionally support Markdown, and I've been sifting through the discussions looking for places to use it. It's my new favorite toy about Relink.

If you had Freelink and Relink, you could choose whether or not to add the child-plugin.

[springer]

Flibbles,

I really value how Relink offers a preview of *where* changes will be made; it's so helpful! Assuming that this kind of preview would be mirrored in the child plugin, and that I could "on the fly" toggle the more "invasive" freelink-relink process on or off as desired, I would probably install the child-plugin as well. Many thanks!

-Springer