I agree completely don’t agree anymore, and hope this request is not forgotten.
Lately I’ve been experiencing several annoying issues with the plugin, so I went to the repo and found out it has a Call for Maintainers · Issue #195 · TfTHacker/obsidian42-strange-new-worlds · GitHub
Hope this inconvenience, and workflow disruption, increase the priority of the current topic. Of course this is in case that implementing Automatic/inline update of links to headings and blocks when they are modified (rename header with no extra dialog window) is not viable.
As I’m exploring a transition from Logseq to Obsidian with Obsidian’s new Logseq importer, I found that with block references and block embeds do import well - but
block-level relationships are lost from Obsidian’s UI:
-
No indicator on a block that it is referenced or embedded elsewhere, and no counter for it.
-
No way to expand a block and see where it is used, in what context.
Proposed behaviour:
-
as proposed in this feature request, blocks that are referenced/embedded elsewhere should show a right-hand link counter (shown in Logseq);
-
clicking it should expand the local referring context (the referring page plus surrounding text, shown in Logseq).
Related: obsidianmd/obsidian-importer#671 — closed as an app-level feature and redirected here.
Micropatches: small fixes and UI tweaks for Obsidian
Micropatches has been a lifesaver, I support and recommend it.