[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A peek to the other side
From: |
Philip Kaludercic |
Subject: |
Re: A peek to the other side |
Date: |
Tue, 22 Feb 2022 19:17:20 +0000 |
"Samuel Banya" <sbanya@fastmail.com> writes:
> The only good thing about VS Code was that it created more LSP servers for
> LSP Mode.
>
> Otherwise, spyware by default is not good for anyone (and yes, it is not easy
> for the average person to remove).
Not only that, but it pushes non-free "plug-ins" that break if you
decided to use a De-Microsofted version of the editor (I believe the
live-collaboration package, and remote access are examples of such
plug-ins, but there are also LSP servers like pylance that per license
are only allowed to be used with MS VS Code).
> Still grateful for LSP Mode :)
>
> On Tue, Feb 22, 2022, at 2:11 AM, emacsq via Users list for the GNU Emacs
> text editor wrote:
>> I tried making a Visual Studio Code extension to see how it could be make
>> more emacs-like if I had to use it for something.
>>
>> If you didn't you don't know how lucky you are with the integrated Elisp
>> manual. It doesn't have an integrated manual, you have to browse a huge HTML
>> file to find some API call :
>>
>> https://code.visualstudio.com/api/references/vscode-api
>>
>> And as usual with APIs (unlike Emacs' open system) you can only access what
>> the developers expose via the API which is very limiting compared to Emacs.
>> You can't change everything, so you don't shoot yourself in the foot. I
>> prefer Emacs' approach where I can even break the system, which is a great
>> learning experience.
>
--
Philip Kaludercic
Re: A peek to the other side, Samuel Banya, 2022/02/22
- Re: A peek to the other side,
Philip Kaludercic <=
Re: A peek to the other side, Arthur Miller, 2022/02/23