flibbles
commented
4 years ago Actually, Relink is designed so you should be able to plug in a handler for a different tiddler type pretty easily. All tiddler text is handled by text.js. All this does is collect together all the relinktextoperator modules. And then when it processes a tiddler's text, it looks for the correct module to the type.
Currently, only one such module exists, in wikitext.js. It's here it exports a function titled text/vnd.tiddlywiki.
All you need to do is create a relinktextoperator module that exports a function like:
/*\
module-type: relinktextoperator
title: $:/plugins/kleinfelter/relink/mmdtext.js
type: application/javascript
\*/
exports["text/markdown"] = function(tiddler, fromTitle, toTitle, changes, options) {
// look in tiddler.fields.text if it contains fromTitle in any form that needs to be updated.
// If yes, set `changes.text` to the text where fromTitle is changed to toTitle.
// otherwise do nothing
}Within it, I guess you can be as complicated as you like. You could do simple regexp find-and-replace for links, or maybe you can integrate with the markdown plugin parser somehow, which is what Relink does with the tiddlywiki wikitext parser.
side note: If you look in text.js, you'll see it quick-rejects tiddlers that don't contain the name fromTiddler. I realize now I'm going to have to move that to wikitext, so don't count on that being there.
kleinfelter
S1E-
cfperez
Gee. All of my non-system/non-plugin tiddlers are Markdown. Where would I need to look to investigate turning Relink loose on Markdown tiddlers? What issues would I need to consider?
(There's a reason why I use Markdown and node.js -- I means that all of my tiddlers are stored in individual Markdown files. That's a pretty safe mechanism if I later decide to migrate to a different product for my personal knowledge base.)