Render text in backlinks, search results, and queries instead of showing raw markdown (reading mode rendering)

after all this while, i feel this should already be implemented. so i’m posting here reasons why it should get priority as a way to solicit the dev team.

there’s no technical limitation to implement

  • as proven by NIL’s query control plugin, it can be done and it could work without significant change or even impact to performance.
  • in fact, the way i see it, implementation can quite unintrusive since it can be an opt-in (as opposed to new redesign implementation in v0.16.0 / v1.0.0 when it impacted many)

there’s no conflict in philosophy

  • having backlinks in rendered markdown is very much aligned to obsidian’s claim that “In Obsidian, making and following connections is frictionless” (as per homepage).
  • on priority, there has been a number of features that aren’t exactly key to obsidian philosophy but got implemented in past year or so such as (a) Callout (even though i love it so much), (b) improvement to Outline plugin (it’s more for long form writing), and (c) popout windows (i don’t know about others, but so far i barely use it).
    • i’m not saying those features should not be there, just to revisit the priority a bit. the way i see it, rendering backlinks (and search) should get higher priority

there are interests from users

  • apart from this post, there are countless forum posts asking for it and related FR such as request for Outline plugin to show as rendered markdown

hope this get their attention :smiling_face:

p/s: also, i’m afraid NIL aren’t going to upkeep the query control plugin (noting that it hasn’t been updated for almost a year…)

11 Likes