@User fyi, update on the lsp work. i've updated dendron's architecture diagram to reflect the lsp and some other changes: https://www.dendron.so/notes/c160ddce-edec-4f6e-841b-418d6030fa37.html#architecture biggest change from what we've originally discussed is that Dendron will not have one but two servers: one lsp server and one express server. found the express server to be necessary because trying to make the vscode language server do anything besides lsp is an exercise in frustration. the lsp server will call into the express server to query the engine. any lookup specific non-lsp functionality will be queried by the extension directly. what's nice about having a standalone local server is that it opens up the path for any longstanding non-lsp related tasks (eg. the pod

sync

feature I was talking about). it will also make it relatively straightforward for any other extension to integrate: instead of having to use a language server client, they can query the server using a traditional REST client. what's nice with this model is that this architecture also migrates well into any standalone/cloud hosted versions of dendron we might pursue in the future.