From: TEC <tecosaur@gmail.com>
To: Russell Adams <RLAdams@AdamsInfoServ.Com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Emacs as an Org LSP server
Date: Tue, 15 Dec 2020 02:12:43 +0800 [thread overview]
Message-ID: <87wnxkntc4.fsf@gmail.com> (raw)
In-Reply-To: <20201214180549.GE6352@maokai>
Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
> REST API calls to a remote server as a core part of editing text in
> your editor isn't concerning? How remote? How would you know? If they
> use HTTPS could you even see what is sent?
I'm not concerned about REST API calls to a remote server, because:
1. There are no REST API calls
2. There is no remote server
> Microsoft doesn't make standards that it can't corrupt or take
> advantage of. See LDAP/AD, HTML extensions, programming language
> extensions that makes their solutions incompatible with standards.
Sure, but I can choose not to support a certain standard, as can other
LSP-Client/Server FLOSS devs, and you can install a particular version
of either.
> REST = web server. Using to make JSON requests over what you are
> editing and your editor requiring the ability to send/receive to a
> potential remote web server is a valid concern.
No REST, just JSON-RPC, which is just a data format. I don't think JSON
is evil. Oh, and once again, no web servers.
> Emacs daemon is a local socket interface (by default) for
> communication between processes on the same box.
Yep, like LSP. Hence the analogy.
> [ MS Taint ]
I'm a stats student, so if you'll excuse the slightly odd perspective, I
see the chance of MS being dodgy as a bayesian process. Previous
knowledge creates an informed prior. It does not allow you to make
conclusions without examining each instance on a case-by-case basis,
only predictions. To do otherwise is to commit the genetic fallacy.
--
Timothy
next prev parent reply other threads:[~2020-12-14 18:20 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 [this message]
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=87wnxkntc4.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=RLAdams@AdamsInfoServ.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).