From: "Samuel Banya" <sbanya@fastmail.com>
To: "Emanuel Berg" <help-gnu-emacs@gnu.org>
Subject: Re: A peek to the other side
Date: Tue, 22 Feb 2022 13:21:04 -0500 [thread overview]
Message-ID: <20b21712-c4a2-496f-ab7b-d0d6d2232ddf@www.fastmail.com> (raw)
In-Reply-To: <V-ctO1QTH0QlQNx4yboyUJLyb8GNAxf3TiExU_ESyb0FfNK-1ASto8S8eRxDuMkPjSEH1Cbk8RF4740KrY_5FP-oyWVtgfaRrVgXuLMSm9s=@protonmail.com>
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).
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.
next prev parent reply other threads:[~2022-02-22 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 7:11 A peek to the other side emacsq via Users list for the GNU Emacs text editor
2022-02-22 16:11 ` [External] : " Drew Adams
2022-02-22 16:46 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-22 18:25 ` Drew Adams
2022-02-22 18:43 ` Eli Zaretskii
2022-02-22 19:38 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26 3:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-23 12:24 ` Arthur Miller
2022-02-23 13:50 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-26 3:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-22 18:21 ` Samuel Banya [this message]
2022-02-22 19:17 ` Philip Kaludercic
2022-02-22 21:31 ` Samuel Banya
2022-02-23 12:05 ` Arthur Miller
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20b21712-c4a2-496f-ab7b-d0d6d2232ddf@www.fastmail.com \
--to=sbanya@fastmail.com \
--cc=help-gnu-emacs@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.
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).