From: Ihor Radchenko <yantar92@posteo.net>
To: Karthik Chikmagalur <karthikchikmagalur@gmail.com>
Cc: "João Pedro" <jpedrodeamorim@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] LSP support in org-src buffers
Date: Mon, 13 Jan 2025 18:53:18 +0000 [thread overview]
Message-ID: <87bjwa7dgh.fsf@localhost> (raw)
In-Reply-To: <87r056zis6.fsf@gmail.com>
Karthik Chikmagalur <karthikchikmagalur@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>
prev parent reply other threads:[~2025-01-13 18:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 5:08 [PATCH] LSP support in org-src buffers Karthik Chikmagalur
2022-10-08 12:50 ` Christopher M. Miles
2022-10-09 7:06 ` Ihor Radchenko
2022-10-11 23:52 ` Karthik Chikmagalur
2022-10-12 6:43 ` Ihor Radchenko
2022-11-21 3:19 ` Ihor Radchenko
2022-11-21 14:39 ` João Pedro
2022-11-22 2:23 ` Ihor Radchenko
2022-11-22 8:21 ` Cook, Malcolm
2022-11-22 8:44 ` Ihor Radchenko
2023-07-27 8:01 ` [TASK] Making org-src buffers sync with real files to allow LSP and other dev tools integration (was: [PATCH] LSP support in org-src buffers) Ihor Radchenko
2022-11-30 4:35 ` [PATCH] LSP support in org-src buffers João Pedro
2022-12-12 13:16 ` Ihor Radchenko
2022-12-15 19:24 ` João Pedro
2025-01-13 17:33 ` Ihor Radchenko
2025-01-13 18:10 ` Karthik Chikmagalur
2025-01-13 18:53 ` Ihor Radchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bjwa7dgh.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jpedrodeamorim@gmail.com \
--cc=karthikchikmagalur@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).