Skip to content

Update neovim docs #50

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update neovim docs #50

wants to merge 3 commits into from

Conversation

nikitabobko
Copy link
Member

No description provided.

Yes, I know that lsp stands for "language server protocol", and thus
what we create should be called just plain "language server"

But LSP abbreviation is ubiquitous and self-explanatory. It's clear what
"kotlin-lsp" means, and it's not so much clear what does kotlin-ls mean.

Additional arguments:
- This git repo is already called kotlin-lsp
- The official nvim lsp integration calls it `kotlin-lsp`
  https://github.com/neovim/nvim-lspconfig/blob/master/doc/configs.md#kotlin_lsp
- The script is called `kotlin-lsp.sh`
Users don't have to interact with low-level `nvim.lsp` API anymore, they
can use the official `nvim-lspconfig`

I'd love to merge neovim.md directly into the README, but given these
lines:

> You can find a standalone LSP launch script in kotlin-lsp.sh along with
> very experimental (aka "works on someone's machine") instructions that
> setup LSP for other editors in scripts folder. See ./kotlin-lsp.sh
> --help for available options.

I don't dare to do so
@nikitabobko nikitabobko force-pushed the bobko/update-neovim-docs branch from 3843d35 to a58c424 Compare June 20, 2025 15:39
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

Successfully merging this pull request may close these issues.

1 participant