[BUG] Using {{value}} or {{mvalue}} in the Capture input dialog causes the application to become unresponsive.

Open aviscaerulea opened this issue 3 months ago • 1 comments

Describe the bug

When calling a Capture with the format setting - {{time}} {{value}} and attempting to save after entering the macro {{value}} in the text input field, the application stops responding.

I suspect the macro is being processed recursively. Another issue is that even code blocks are likely being treated as macros.

In “Capture,” configure the following format settings:

Use {{value}} as a code string as shown below. The same issue occurs with {{mvalue}}.

Sep 14 '25 08:09 aviscaerulea

You could help anyone working on this by providing the output of Obsidian’s Show Debug Info command.

Sep 20 '25 18:09 claremacrae

:tada: This issue has been resolved in version 2.9.4 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket:

Dec 18 '25 14:12 github-actions[bot]