Mario Pietsch

hmmm, That's OK for ``` {{}} ``` But it is still a problem with "unfinished" code as follows. ``` ```

I do think that this PR is an improvement for many users already. I think it should be included. But I also think, that we need a runtime fix for...

@bluepenguindeveloper -- I am creating a second PR atm, which tries to solve the "runtime" side of that problem. From time to time I'm also a "victim" of that problem...

Can you please cover the "shared code" in a pretty-link, so we do not have this "ugly link" in the PR

>I actually do want the non-persistent library tiddler feature, so I might make use of this, except it looks like a bug which might get fixed out from under me....

I did a second check. -- Both the editions/fr-FR and the editions/dev (the core dev edition) seem to use the .if-macro. I'll create an "Export doc macros" button, which should...

I think adjusting the Theme Tweaks according to the theme is a good idea. BUT "layouts" are no "themes". Themes are plugins, which can overwrite the "Theme Tweaks" tabs if...

> Their is also no obvious/standard way for an author of a new Layout to add theme settings/tweaks in the default UI. I did have a closer look and that's...

>Hi @pmario this change is not backwards compatible. Inspecting the DOM output, we've lost the tag that should be the first child of . There is no `` code in...

> Apologies @pmario I was mistaken. Looks good to go Hmm, The funny thing is, that this PR would have created an extra P tag, that would have caused formatting...