Mario, It would be simple to enhance the update process to report on the core shadow tiddlers it changed that have a "tiddler" (rather than Shadow) and give the user the ability to review the differences and decide what to do (accept -trash tiddler, ignore -keep tiddler, edit - update new core with edited tiddler). Alternatively a "post update" review.
As I understand it the update currently just replaces mostly the $:/core plugins, if not all, even if they don't change. Regards Tony On Thursday, 6 May 2021 at 18:55:14 UTC+10 PMario wrote: > Hmmm, > I think, that's not very practical. As soon as you want to link to a TW > shadow tiddler, you create a clone as a side effect. > > IMO linking needs to be side-effect free! Those edited shadows are > "system" tiddlers. System tiddlers are "user content" and the use always > wins. So those tiddlers will not be updated, if a new core will be used. > > So linking will break the update mechanism > > Just a thought. > -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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a0baf8ef-8be0-4234-9daf-67628e31f755n%40googlegroups.com.
