Karthik Chikmagalur <karthikchikmaga...@gmail.com> writes: > After trying it for a while, my opinion is that this way of getting LSP > support is a hack and somewhat fragile. This is why I haven't worked on > it since.
I was more referring to the idea with tangling https://gist.github.com/bigodel/15599f3c1da23d1008b7d7d4ff8bff77 shared by Joao. > ... On the Eglot repo, they're considering adapting LSP's jupyter > notebook support to source blocks in Org: > > https://github.com/joaotavora/eglot/issues/523#issuecomment-2542536622 > > There are some limitations: > > - This requires some work on the Eglot side, specifically a new minor > mode that sets some Eglot state variables. > > - I don't think many language servers include notebook support. > But the support might be better than the background-tangling approach > used by proposal in this thread. I agree that it would be best to make use of the native langserver capabilities, if they are available. However, tangling approach is much more universal. It will cover more than just LSP servers - other traditional dev tools as well. So, there is a lot of value in having that independent of dedicated eglot/lsp support. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
