Open smarj opened 1 year ago
Yeah regex based parsing tends to do that, I suppose. For now, you can get around it by changing the character used to prefix inline queries in the plugin settings.
This still occurs with '=', I get around it by using lateX $=$ for in-line rendering
What happened?
The following literal text, which was part of a task, and not intended to be an inline field:
Produces a parsing error:
DQL
No response
JS
No response
Dataview Version
0.5.47
Obsidian Version
1.0.3
OS
MacOS