>> We are not in hurry. Any progress will be appreciated as long as there >> is some. > > Unfortunately, this important patch is stuck. > It would be nice is somebody revived the work on it. > Anyone interested will do, not just people involved in this thread :)
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. 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. Karthik
