[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 09:50:26 +0000 |
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.
--
Philip Kaludercic
- Elisp LSP Server, Ag Ibragimov, 2021/10/05
- Re: Elisp LSP Server, Po Lu, 2021/10/05
- Re: Elisp LSP Server,
Philip Kaludercic <=
- Re: Elisp LSP Server, Po Lu, 2021/10/05
- Re: Elisp LSP Server, Philip Kaludercic, 2021/10/05
- Re: Elisp LSP Server, Richard Stallman, 2021/10/06
- Re: Elisp LSP Server, Philip Kaludercic, 2021/10/06
- Re: Elisp LSP Server, Stefan Monnier, 2021/10/06
- Re: Elisp LSP Server, Richard Stallman, 2021/10/07
- Re: Elisp LSP Server, Po Lu, 2021/10/06
- Re: Elisp LSP Server, Ag Ibragimov, 2021/10/10
- Re: Elisp LSP Server, Daniel Martín, 2021/10/10
- Re: Elisp LSP Server, Philip Kaludercic, 2021/10/10