Results 216 comments of Moritz Jung

I haven't troubleshot this yet, but my first guess would be that this is either a result of how meta bind interacts with templater or an issue in templater.

Can you provide a reproducible example of this behavior?

I will close this for now. You can reopen this or another issue when you finish your write-up.

I am just going to list my opinion on your proposed changes in no particular order. - I don't like expandable sections, I much prefer the button templates to stay...

You can already achieve that with `replaceSelf` and an empty replacement string.

Yep, because of a limitation in the Obsidian API. There is no way for inline buttons to know where in the file they are, and they need that to replace...

The same string of text might occur multiple times in the file, or even as part of something else which is not an inline button declaration. So doing a simple...

How exactly should that API work? You give the API just the field declarations like `INPUT[number:someComputedValue]` and it returns the value in plain markdown, so `2`?