I would also very much +1 this feature. The panes in which search results, tag list, links/backlings content etc. appear, have by themselves much less contrast and smaller character than the editor view. Thus, I would argue that especially here the rendering of content creates a huge, huge benefit. I frequently feel lost in the forest of syntax while trying to skim the content. Having this said, also the type of activity that you normally do on this type content - skimming - requires better orientation, facilitated by rendering. I normally do not become distracted by looking at markdown syntax, I even wrote my entire doctoral thesis in vim with pandoc markdown. But this is writing, it is a different, normally slower and more elaborated process than skimming across a long list of diverse content and looking for the one piece of information, or getting an overview. Rendering would make this a lot more pleasant.
Render text in backlinks and search results instead of showing raw markdown (reading mode rendering)
Although I use Obsidian already quite some time I have rather seldom used the backlinks feature. Only now starting to realise how valuable it is, but also why I did not use it as much as I could.
The reason is the presentation. I have tried Logseq recently to see how that works and the backlinks work a lot better there because they are formatted and they only show the block where the backlink originates from.
Now Obsidian allows you to hover over the block to preview it but I would like to have an option to always show the backlink previewed and limited to the correct block (as it does already but only in edit format).
It seems like the code is already available. Just make the preview format the default for the backlinks and also show only the whole block that is referenced.
Im upvoting this and make it current. I really want the reading view formatting for backlinks (coz I use it alot). In fact I am use it also via embedded query, so it would improve my workflow even more.
Hope to see this in the trello roadmap soon 
@moderators I guess, title of this request should change from Display search results and backlinks in preview mode e.g. to:
Display search results and backlinks in "Reading view" mode
To keep it consistent with updated naming convention from https://forum.obsidian.md/t/obsidian-release-v0-13-8-insider-build/28329 :
- “Preview mode” has been renamed to “Reading view” to avoid confusion.
+1
This is the feature I’ve been waiting for the most since the day Obsidian appeared!
It would improve so many features at once: side pane backlinks, in-file backlinks, file search, embedded queries.
Right now it looks, well, suboptimal, especially in bullet lists, since the indentation gets lost once the line gets wrapped:
And there are a lot of folks who use Obsidian as an outliner: the outliner plugin has more than a hundred thousand downloads right now!
The latest version of the Query Control plugin can now render search results in the sidebar search and in embedded queries.
The plugin adds an extra button to the nav bar which allows you to render your results. See the release notes here for more details: Release 0.3.0 · nothingislost/obsidian-query-control · GitHub
The plugin is still in early development but can be installed using the BRAT community plugin by adding the beta repository “nothingislost/obsidian-query-control”
Looks like the plugin development is somewhat haphazard. I also see the author resorting to monkeypatching to achieve this. This might be brittle, and besides, I just don’t see the point of having your search results not rendered.
Trying out the plugin makes it even clearer, that rendering search results is a much cleaner & user-friendly way of displaying them.
+1 to this.
I liked the plugin so much that I made it a template for all my daily notes to replace the backlink. It just looks so much better with the search results rendered.
If this can be incorporated to the core backlinks plugin that woukd be amazing!
I’d actually like to see Markdown-rendered backlinks in any mode (live preview), not just reader mode.
Furthermore, it would be easier for me to find backlinks at the bottom of the main page view rather than hidden in a side panel (as an optional setting). My ideal would be to treat each backlink as a collapsable transcluded link to the heading section / block section they are in, and make it possible to edit the transcluded sections (which itself is another FR: Edit transcluded (embedded) notes (blocks) in place (likely requires WYSWYG first)).
I understood the purpose of this feature request is to display content of a backlink as rendered html instead of raw markdown. In my previous post I aimed to keep integrity of currently used Obsidian terminology.
Not that someone would want to restrict behavior of backlinks based on currently active mode in some pane.
So If I understand you correctly, our preferences are the same, aside of editable transclusion which is separate request.
Obsidian → Settings → Plugin Options → Backlinks → toggle “Backlinks in document”
Does it solve the quoted issue?
Yeah, thanks for the setting link. That is close enough to what I’m looking for for the time being.
As this feature request seems to be about preview/reading mode, does it also cover live preview? Or should I open a new thread?
(The mentioned examples of logseq and the query-control plugin suggest it is also about live preview, but the terminology seems more about reading view)
The search results should use the same markdown rendering as the live preview/reading view.
Sounds sensible. Should it be renamed to ‘Use selected mode for search results and backlinks’ or something?
+1 on this, would make backlinks a lot friendlier
For anyone who is interested in the topic of “rendering the search result”, you may have a look at and have a try of the beta plugin introduced here.
The author of this plugin had finished the part of rendering the query command resul and search panel result. The only think that is left is the rendering of the backlink result. And a feature request had been proposed to the author of the plugin for 3 months, but no further reply on if from the author.
I’m not the author of the plugin and not familiar with the TS/JS, so if any one who is familiar with the TS/JS may have a look at the code on github, and see if you can work it out.
Also, the developer of Obsidian may have a look at of the code as well. I think this feature could be a core plugin.
