emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Gerry Agbobada" <emacs-orgmode@gagbo.net>
To: "General discussions about Org-mode." <emacs-orgmode@gnu.org>
Subject: Re: Emacs as an Org LSP server
Date: Mon, 14 Dec 2020 18:27:17 +0100	[thread overview]
Message-ID: <5b6aab88-80c1-441b-bd69-fefa50bdd11f@www.fastmail.com> (raw)
In-Reply-To: <X9eak3kRHOvFwexX@protected.rcdrun.com>


[-- Attachment #1.1: Type: text/plain, Size: 2758 bytes --]


> It may all look nice and shiny. But what you people don't understand
> is that it is Microsoft and deep meaning of Microsoft one can know if
> one researches the history as only so one can see the present and look
> into future. Microsoft never changed its strategies. Language server
> protocol is just another branch of possible strategies to take away
> people's computing. It is matter of advertising and making it popular,
> when all the fish are in the net that is where final result comes, and
> that is to take away people's freedom and computing to centralized
> places.
> 
> 

Hello,

You made is a very clear point about _not_ understanding that "server" does not mean "machine controlled by Microsoft". As long as you refuse to understand that, it's very hard to discuss seriously on the matter. I attached as a picture how I plan to summarize LSP to new Doom Emacs users that don't know much about Emacs either. Hopefully this will be clear enough and show that :
- The "server" program does not need to run in the cloud/on 3rd party hardware (it would be really inefficient actually, since everything is IO bound when it comes to LSP)
- You can use any server program you want, even a GPLv3 and later software in the complete stack if you want.

Furthermore, I find that spending so much time and energy to prevent people from spending their time on what they think is right, is pretty harmful.

With that out of the way :

> If Microsoft is really so friendly, then instead of server based
> language service they could provide generic definitions how editor
> could act, and editor could load those generic definitions locally
> without server/client paradigm.
This is literally what MS did.
The protocol is entirely public : https://microsoft.github.io/language-server-protocol/ Of course the governance is terrible and MS might choose to change the protocol in a non-forward compatible once "all the fish are in the net" and they want to force everyone to use VSCode because it becomes the only client that's fully compliant.

Even if that were to happen, nothing prevents people to say "I don't want to follow MS protocol anymore, the program I distribute as LSP server follows the last protocol version I agree with, i.e. 3.15" and linking to that protocol. the LSP clients that want to use that lsp server to enhance editing capabilities (or allow smart manipulations of org-files from editors that are not Emacs*) for org-mode files will have to follow the 3.15 protocol if they want the features.

* which seems to be the goal of this endeavour.

I don't feel like answering much more about this subject, I'm more interested in the technical stack to make that thing work than the usual GNU politics to be honest.

Gerry Agbobada



[-- Attachment #1.2: Type: text/html, Size: 3491 bytes --]

[-- Attachment #2: lsp-doom.png --]
[-- Type: image/png, Size: 253038 bytes --]

  parent reply	other threads:[~2020-12-14 17:32 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
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 [this message]
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=5b6aab88-80c1-441b-bd69-fefa50bdd11f@www.fastmail.com \
    --to=emacs-orgmode@gagbo.net \
    --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).