Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define standards for describing LSP servers. #138

Open
PerilousBooklet opened this issue Dec 1, 2024 · 0 comments
Open

Define standards for describing LSP servers. #138

PerilousBooklet opened this issue Dec 1, 2024 · 0 comments

Comments

@PerilousBooklet
Copy link
Contributor

PerilousBooklet commented Dec 1, 2024

As suggested by Guldoman, we should define a standard descriptive convention for LSP server entries, to keep them neat and tidy.

For the naming convention we could do something like name_ls ( svelte_ls, tailwindcss_ls, ...).

For the description, we could write something like the following:

---# language_name - lsp_server_name
--- __Status__: Untested/Works/Works Partially
--- __Site__: https://github.com/user/lsp_server_name
--- __Installation__: ...
--- __Note: ...

The Perl entry is a good example:

---# Perl - Perlnavigator
--- __Status__: Works
--- __Site__: https://github.com/bscan/PerlNavigator
--- __Installation__: `paru -S perlnavigator`
@PerilousBooklet PerilousBooklet changed the title Define standard for naming LSP servers. Define standard for describing LSP servers. Dec 1, 2024
@PerilousBooklet PerilousBooklet changed the title Define standard for describing LSP servers. Define standards for describing LSP servers. Dec 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant