Incorrect TeX expression in quote block breaks indexing

Help
1

Before opening a new bug report, please search the forum for duplicates and follow the Troubleshooting Guide.

  • We only consider bugs that are reproducible in the sandbox vault or a vault with no third-party plugins/no css snippets/default theme.
  • For Linux, we only accept bug reports that are reproducible with our Appimage or Snap package under Gnome or KDE.
  • Developer issues with the API should go here
  • Themes and Custom CSS issues should go here
  • Obsidian Clipper Bugs should be posted here
  • Obsidian Importer Bugs should be posted here

Once you’ve done the above, delete everything above this line.

Steps to reproduce

This works

## heading 1
>$$ expr
>$$
## heading 2

i.e. the following block finds both headings

[[# heading ]]

This breaks the second heading

> $$ expr
$$

Did you follow the troubleshooting guide? [Y/N]

Expected result

since the entire expression is rendered as part of the quote block, the tex expression should be contained in the quote block even if it’s on a line without explicit quote prefix (“>”)

Actual result

Rendering works, but indexing breaks silently.

Environment

SYSTEM INFO:
Obsidian version: v1.8.1
Installer version: v1.7.6
Operating system: Darwin Kernel Version 24.3.0: Tue Dec 17 23:24:24 PST 2024; root:xnu-11215.80.28.501.2~1/RELEASE_ARM64_T6000 24.3.0
Login status: logged in
Language: en
Catalyst license: vip
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on

RECOMMENDATIONS:
none

Additional information

This is a silent functionality breaking that’s hard to find and debug

2

We are not going to support this.
The only syntax we support for math blocks we support is
$$math$$
OR

$$
math
$$

and for quotations
> $$math$$
OR

> $$
> math
> $$

The docs will be updated to reflect this.

3

Thanks for clarifying.
I think that’s ok, however the problem is indexing silently fails and the bug is that it actually renders correctly / doesn’t display an error.

If rendering works accidentally, although it shouldn’t, why don’t you then break the TeX rendering (and / or display an error)?

It should work consistently to how an open code block (```) renders all remaining text as code.