blacksmithgu / obsidian-dataview

A data index and query language over Markdown files, for https://obsidian.md/.
https://blacksmithgu.github.io/obsidian-dataview/
MIT License
6.94k stars 411 forks source link

Parse error when I'm not using an inline field #1579

Open smarj opened 1 year ago

smarj commented 1 year ago

What happened?

The following literal text, which was part of a task, and not intended to be an inline field:

the `=` instead of `:` problem

Produces a parsing error:

the Dataview (inline field "): Error:
-- PARSING FAILED - - -.

Got the end of the input
Expected one of the following:
"(' 'null', boolean, date, duration, file link, list ('[1, 2, 3]'), negated field, number,
object ('{ a: 1, b: 2 }'), string, variable
or: choice

DQL

No response

JS

No response

Dataview Version

0.5.47

Obsidian Version

1.0.3

OS

MacOS

AB1908 commented 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.

KingPsychopath commented 9 months ago

This still occurs with '=', I get around it by using lateX $=$ for in-line rendering