Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75966 - [vscode-languageservers] Include symlinks to *-language-server

Attached to Project: Community Packages
Opened by Yangtse Su (yangtsesu) - Wednesday, 21 September 2022, 04:26 GMT
Last edited by Daniel M. Capella (polyzen) - Thursday, 22 September 2022, 01:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Daniel M. Capella (polyzen)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The executable was expected to be 'vscode-html-language-server' in neovim and helix.

Additional info:

https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#html
https://docs.helix-editor.com/lang-support.html
This task depends upon

Closed by  Daniel M. Capella (polyzen)
Thursday, 22 September 2022, 01:44 GMT
Reason for closing:  Implemented
Additional comments about closing:  https://github.com/archlinux/svntogit-co mmunity/commit/c17d8a8b4b720abfd7b188180 bcebc74f3a3d179
Comment by Daniel M. Capella (polyzen) - Wednesday, 21 September 2022, 07:16 GMT
https://github.com/neovim/nvim-lspconfig/pull/1288#issuecomment-932396196

I create symlinks locally to appease lspconfig, but perhaps I should just add them to the package.
Comment by Yuji Nakao (ynakao) - Wednesday, 21 September 2022, 11:13 GMT
I also encountered the same naming issue when configuring lsp-mode in Emacs.

https://github.com/emacs-lsp/lsp-mode/issues/3705

It seems installing HTML/CSS/JSON language server from `vscode-langservers-extracted` is the de-facto standard on other OSes and Linux distributions.

I also believe it is preferable to name binaries respecting vscode upstream. However, `vscode-langservers-extracted` doesn't accept filling any issues, and such renaming would force the current LSP client ecosystem to change their configurations, so renaming on Arch side or symlink solution as polyzen said would be better for the time being, I think.
Comment by Yangtse Su (yangtsesu) - Wednesday, 21 September 2022, 14:14 GMT
I'm sorry. So that this is the problem of neovim lspconfig and Helix, Since 'vscode-json-languageserver' is being used in upstream.
But obviously neovim lspconfig does not mean to correct it. Creating links is a temporary solution.
Of course, another option is to modify the 'cmd' parameters in neovim-lspconfig, lsp-mode, and Helix.

Loading...