Whenever I edit a Block (or open the mearkdown file) I only see an ID and have no idea what is that about. I have to exit Edit Mode to see the Block Ref turn into a virtual Link that takes the Title of the Referenced Block and shows it on screen.
Why not use the
() Inline Link to place in the Link Text the Referenced Block’s Title (or a part of it if it’s too long) and use the Ref ID in the Destination just like currently done with Inline Links of Logseq Pages:
[some inline text ]([[Some Page Name]] ).
I suggest Logseq adopts the following for Block Refs:
[extracted referenced block title or max 50(?) characters](((Block ID)) "[[Page Name where the Block is in]]")
This would provide so much more context for the barren Block IDs.
PS: I am doing that manually atm and it’s sooo painful to get to the level on context I need when I reference a Block…
You may have better luck using a editor that supports LSP and try this one for Logseq:
Once setup you should be able to hover an embedded block and see its content.
Whenever I insert a Block-Ref I actually get the Title of that Block in Logseq GUI and I see what it is about. I want that to not only be some virtual rendering on Logseq’s part but Logseq to bake-in that virtual Link Text into the actual Markdown in the form of a Markdown Inline Link. I’ve seen ORG Mode has something similar.
I wish I understood more from that LSP github page …
You need a editor that support LSP (language server protocol) like VS Code. LSP is a way to get IDE-like features like code completition for different programming languages, without the need to reimplement everything in each editor.
That GitHub repo has a release page with a binary you should download and put in a specific folder (in Linux and MacOS is called $PATH).
Then each editor need a simple config file to add a new LSP server and in that GitHub repo there is an example that can be adapted to other editors like VS Code.