[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Elisp LSP Server

From: Philip Kaludercic
Subject: Re: Elisp LSP Server
Date: Tue, 05 Oct 2021 11:46:23 +0000

Po Lu <luangruo@yahoo.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>> Po Lu <luangruo@yahoo.com> writes:
>>> Ag Ibragimov <agzam.ibragimov@gmail.com> writes:
>>>> Another reason: VSCode. The damn thing is spreading like a
>>>> disease. And now it's even possible to browse code on GitHub, in a
>>>> browser, by simply pressing <.> (the dot).  I would love to be able to
>>>> comfortably browse through elisp code without having to clone it
>>>> locally, but none of the existing VSCode Lisp plugins are any good.
>>>> For example, there's no equivalent of imenu for Lisp files. You can't
>>>> jump to a given function.
>>> Isn't the code behind that particular feature proprietary?
>> In what sense? GitHub is inherently proprietary, so yes, but what
>> about this specific feature is different.
> I think it is dangerous for Emacs to "integrate" with such proprietary
> software.  It would make people gravitate towards that software.

That yes, but that is an inherent problem of LSP (e.g. see how VSCode
can automatically download and run a propitiatory LSP server like
Pylance), and not the "." command itself.

I think a better solution to Ag's problem is to make editing online
repositories easier, without to manually clone a directory every time.

        Philip Kaludercic

reply via email to

[Prev in Thread] Current Thread [Next in Thread]