From: George Mauer <gmauer@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Emacs as an Org LSP server
Date: Sun, 13 Dec 2020 19:10:44 -0600 [thread overview]
Message-ID: <CA+pajWLYpBcDZXp0Ux5Y4GonJBYdL4y_untcEkJoUcHXDE5w+Q@mail.gmail.com> (raw)
In-Reply-To: <X9Z4Pq0oDVw9XNzq@protected.rcdrun.com>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
I think maybe you might be thrown off by the word "server"? Lsp is just a
standardization of how an editor can do language-specific things. The fact
that standardization exists makes the whole thing pluggable by various
services. These typically run in a separate process - which is a good idea
anyways - on the same machine and the plugin just starts that prices and
communicated to it.
Typescript, c#, I think python, and JavaScript (and maybe Java?) plugins
already do this
On Sun, Dec 13, 2020, 14:34 Jean Louis <bugs@gnu.support> wrote:
> * TEC <tecosaur@gmail.com> [2020-12-13 20:35]:
> > > From a perspective that some server has to know what user is writing
> > > it is advisable to use one own's servers. But if idea gets popular
> > > some company will commercialize it and centralize user's data and
> > > privacy is gone.
> >
> > FYI the nature of LSP (as I understand it) is that the "server" is a
> > locally running service that responds to signals from a "client" (code
> > editor / IDE).
>
> That is how it starts until corporation like Github or somebody else
> takes it over. Just look at Github pattern. Git was decentralized
> system that they centralized for 50 million developers and included
> eye candies that one cannot self-host as one wants.
>
> Jean
>
>
[-- Attachment #2: Type: text/html, Size: 1758 bytes --]
next prev parent reply other threads:[~2020-12-14 1:11 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
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 [this message]
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=CA+pajWLYpBcDZXp0Ux5Y4GonJBYdL4y_untcEkJoUcHXDE5w+Q@mail.gmail.com \
--to=gmauer@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).