From: TEC <tecosaur@gmail.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Emacs as an Org LSP server
Date: Sun, 13 Dec 2020 18:41:58 +0800 [thread overview]
Message-ID: <87v9d66l75.fsf@gmail.com> (raw)
In-Reply-To: <87o8kf69tm.fsf@ucc.asn.au>
A little progress update.
https://github.com/tecosaur/org-lsp now exists.
I have no idea what I'm doing, so if anyone has feedback on the current
idea, that would be much appreciated.
TEC <tecosaur@gmail.com> writes:
> Hi Everyone,
>
> From the Org standardisation effort the idea of using Emacs as the basis
> of an LSP server for Org has been mentioned a few times.
>
> I thought this deserved it's own thread so here it is :)
>
> I'm quite keen to investigate the viability of this idea.
> Some key questions that I think need addressing are:
> 1. How can we 'package' Emacs into an LSP client?
> 2. Assuming we use some language as the basis for the host how do we
> want to pick it? LSP library? Lisp? Are there any outstanding
> contenders.
> 3. How much effort is involved? Is it worth it to try to make Org more
> approachable* (without Emacs)?
>
> Lastly, but perhaps even more crucially --- who would be interested in
> working on this? I certainly am, but this feels like something that
> would be more viable with a small working group.
>
> Who's interested?
>
> Timothy.
>
>
> * I can't help but think that this hypothetical LSP server may serve as
> a 'gateway drug' to Org in Emacs 😉
next prev parent reply other threads:[~2020-12-13 10:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:05 Emacs as an Org LSP server TEC
2020-12-13 10:41 ` TEC [this message]
2020-12-13 11:05 ` Bill Burdick
2020-12-13 14:36 ` Jean Louis
2020-12-13 17:33 ` TEC
2020-12-13 20:23 ` Jean Louis
2020-12-14 0:54 ` Gerry Agbobada
2020-12-14 1:04 ` Tim Cross
2020-12-14 1:10 ` George Mauer
2020-12-14 11:41 ` Neil Jerram
2020-12-14 15:25 ` TEC
2020-12-14 15:46 ` Neil Jerram
2020-12-14 15:55 ` TEC
2020-12-14 17:02 ` Jean Louis
2020-12-14 17:08 ` TEC
2020-12-14 18:05 ` Russell Adams
2020-12-14 18:12 ` TEC
2020-12-14 19:16 ` Russell Adams
2020-12-14 20:18 ` Jean Louis
2020-12-14 21:34 ` Tim Cross
2020-12-14 20:20 ` Tim Cross
2020-12-14 21:45 ` Tom Gillespie
2020-12-14 18:39 ` LSP is Microsoft's patented protocol - " Jean Louis
2020-12-14 18:44 ` TEC
2020-12-14 18:52 ` Jean Louis
2020-12-15 5:47 ` Richard Stallman
2020-12-15 5:50 ` Jean Louis
2020-12-15 6:09 ` Christopher Dimech
2020-12-15 6:25 ` Jean Louis
2020-12-15 6:51 ` Christopher Dimech
2020-12-16 5:38 ` Richard Stallman
2020-12-14 17:27 ` Gerry Agbobada
2020-12-14 18:16 ` Jean Louis
2020-12-14 18:26 ` TEC
2020-12-14 18:50 ` Jean Louis
2020-12-14 19:41 ` Russell Adams
2020-12-14 18:51 ` Bastien
2020-12-15 8:51 ` Bill Burdick
2020-12-14 19:50 ` Tim Cross
2020-12-14 21:51 ` Jean Louis
2020-12-14 22:35 ` Dominik Schrempf
2020-12-14 23:36 ` Jean Louis
2020-12-14 17:22 ` Neil Jerram
2020-12-14 17:24 ` TEC
2020-12-14 17:57 ` Neil Jerram
2020-12-14 18:04 ` TEC
2020-12-14 17:39 ` Russell Adams
2020-12-14 17:45 ` TEC
2020-12-16 11:49 ` Bastien
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=87v9d66l75.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).