What you say is correct, Jeremy, and I'm already version controlling my wiki and keeping my personal customisations in plugins, and yet... your comments trigger a couple of thoughts.
The first is that TW is "marketed" as a personal notebook as much as a personal wiki. The second sentence at tiddlywiki.com is "Welcome to TiddlyWiki, a unique non-linear *notebook* for capturing, organising and sharing complex information." If TW is intended for use by ordinary computer users, as opposed to software experts or power users, it may not be reasonable to expect them to be git wizards able to use git bisect and others techniques to track down a breakage. The other thought is that I've seen several suggestions in this group that TW is in the first stages of an explosion of creativity/development/customisation now that it has reached a sufficient degree of maturity. If true, this is going to expose a great deal more of the brittleness you refer to as multiple plugins and components interact with each other. For example, a recent topic reported that two plugins both replaced the same core tiddler, breaking one (or was it both?) of them. As another example, AFAIK TW won't warn a user if they create or import a tiddler, or install or upgrade a plugin, that overwrites a variable, macro or filter defined in an existing tiddler/plugin; nor is there a canonical list available anywhere that lists variables, macros and filters provided by custom plugins, so developers of new plugins (or just personal customisations) can avoid name collisions. (This risk can obviously be minimised by plugin- or user-specific prefixes.) These comments are made as a recent convert to, and huge fan of, TW(5). Regards, David. On Sat, 2 Mar 2019 at 23:42, Jeremy Ruston <[email protected]> wrote: > I think the problem you’re describing is the possibility that ones > delicate arrangements of customisations might break, perhaps through an > upgrade or human error. That’s certainly something I can relate to, and I’m > interested in how we can address the brittleness of complex wikis. > > The primary defence is to keep continuous backups. > > Further defences include making your customisations into a plugin. > -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/CAFWVPz_P8ZR92Y8hqrdXsyjoYGiCPAVAOFNtqT09%3DxJNckrDug%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
