From: Ihor Radchenko <yantar92@posteo.net>
To: "João Pedro" <jpedrodeamorim@gmail.com>
Cc: Karthik Chikmagalur <karthikchikmagalur@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: [PATCH] LSP support in org-src buffers
Date: Tue, 22 Nov 2022 02:23:55 +0000 [thread overview]
Message-ID: <87a64jd8w4.fsf@localhost> (raw)
In-Reply-To: <87sficbccx.fsf@gmail.com>
João Pedro <jpedrodeamorim@gmail.com> writes:
> I think the contextual src block could be split from the LSP
> functionality, since it could be used in other contexts other than
> dealing with language servers. My iteration is not tied to anything in
> particular and simply creates a source buffer with the whole context for
> that tangled file.
>
> Hope this can help you in some way!
>
> [1] https://gist.github.com/bigodel/15599f3c1da23d1008b7d7d4ff8bff77
It looks like you have done something very close to what we are
discussing. Would you be interested to create a patch against Org core
instead of relying on advises?
--
Ihor Radchenko // yantar92,
Org mode contributor,
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>
next prev parent reply other threads:[~2022-11-22 2:24 UTC|newest]
Thread overview: 14+ 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a64jd8w4.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.