On Thursday, April 2, 2015 at 11:20:01 AM UTC+2, Mat wrote: > > I'm always a bit hesitant in modifying core tiddlers. On the one hand I > guess I should be... but then, hacking is what TW is about. >
That's why there is the warning if you open a core tiddler. > But first there's the "what if I break something". While I guess that is > possible, am I right in that in most cases I can just delete the tiddler > and the core will re-use the original? > Don't use "production" for your experiments, without a backup. __Backup__ is the key word here! ... If you break something, but the edit / save mechanism still works you just delete your modified tiddler and the core tiddler will take over again. ...and what does that mean actually, that it created a copy as soon as I > started to modify it? > yes. Second, there is the updating aspect. Modified core tiddler, not update to > it. > If you modify a core tiddler, you don't get core updates to this tiddler anymore, because your modification will take precedence. ... That's intended by design! > Now, I'm wondering if there actually is a copy kept of the original, then > why can't we let this copy be updated so that if I delete my modified > version then I revert back but to an updated original. > That's the case. The core is only 1 plugin, that contains all the tiddlers. The core will be updated, including your modified tiddler. But since your tiddler is activated later, your modification will overwrite the updated core. -mario -- 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 http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b8e3d5a0-19fe-4be7-acc8-60b1071598e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
