Whitespace weirdness randomly limits headings detection

Bug graveyard
1

Steps to reproduce

I write a daily journal. Sometimes after I type heading hashtag, for some reason Obsidian does not recognize it in preview or inline-preview mode. Even after saving and reloading. I also wrote the journal with Typora, everything looks ok there but when I open it on Obsidian, some headings are detected and others are not. I haven’t been able to recognize a pattern.

When I delete the whitespace between the hashtags and the heading, it magically fixes the problem! I’m baffled.

I’ve tried with inline priview, without preview, with safe mode, etc. Im using the standard theme.

Expected result

Properly render headings.

Actual result

Just see the actual hashtags in preview, as if they were being escaped.

Environment

  • Operating system: MAC OS Monterey 12.1
  • Debug info:
    SYSTEM INFO:
    Obsidian version: v0.13.21
    Installer version: v0.12.19
    Operating system: Darwin Kernel Version 21.2.0: Sun Nov 28 20:28:54 PST 2021; root:xnu-8019.61.5~1/RELEASE_X86_64 21.2.0
    Login status: logged in
    Catalyst license: insider
    Insider build toggle: on
    Live preview: on
    Legacy editor: off
    Base theme: light
    Community theme: none
    Snippets enabled: 0
    Safe mode: on

RECOMMENDATIONS:
none

Additional information

See videos here: Dropbox - Obsidian.mov - Simplify your life
Dropbox - Obsidian 2.mov - Simplify your life

2

How do I reproduce this? Do you have steps?

Can you attach a file where it doesn’t work?

3

I started to write like a madman to try and see a pattern. I think that I got it!

Hashtag sign # on my keyboard is option (alt) + 3. When I keep option key pressed and then spacebar, a whitespace is written but it looks like it’s a different character because Obsidian does not recognize it as a whitespace! Other MD editors I use: Typora, Devonthink doesn’t have this issue.

Test markdown:
https://www.dropbox.com/s/nqhhx8uwghobig3/999999999999%20Test%20markdown.md?dl=1

4

Thank you. You are likely entering a “non-breaking whitespace”.
This is not commonmark compliant, Obsidian is behaving correctly so this is not a bug.

1 Like