Mario Pietsch

I did have a look and was a bit confused. - The system dialogue says: edit - copy - delete - If I click **edit** I get: view - copy...

The "Choose an image" dropdown is almost invisible with "dark" palettes  Especially "Spartan Night" seems to have a problem

See my comment at: https://github.com/TiddlyWiki/TiddlyWiki5/issues/8497#issuecomment-2277283396

>Since the macro is neither used by the exporter (it appeared only once in the file) nor used by other system macros (searching exportButtonFilename only have 1 result). I think...

That's my take on how to make the existing code human readable: https://github.com/TiddlyWiki/TiddlyWiki5/pull/8504/files?diff=unified&w=0 It does **not** contain any new functionality

I think there may be some "still useful" branches for you. In your jermolene repo, you can keep as many branches as you like. But I think in the tiddlywiki...

>The web interface makes it difficult to delete lots of branches at once, but perhaps we can cook up a command line script. Manually deleting merged branches is probably 5...

I am OK, if there are 5 to 10 WIP branches in the organisation repo. We are used to it but there are 90+ and growing, because of already merged...

I think, that the full description of the plugin-history should be part of a demo-edition. The plugin itself should only contain the minimal changelog-info. Over time there may be plugins,...

>With the scheme I outlined it is entirely up to the plugin publisher how much information they retain. That's right. But I was thinking about core plugins. We should also...