Probably should have anticipated this, but people are confused about nvim-lsp (this repo, not Nvim-builtin) vs vim.lsp (Nvim builtin). Although the nvim-lsp README.md makes it clear, it still confuses people in discussions (example), and people who are just getting started.
So we should
nvim-lsp.configsrequire'nvim_lsp' is distinct from vim.lsp, since their names are semantically equivalentI will do so in the next ~week if there are no objections.
cc @norcalli
No objections. I'm curious if github will handle redirection for cloning, though. It's probably worth a test run on a dummy repo.
@norcalli
It automsticaly redirects.
https://help.github.com/en/github/administering-a-repository/renaming-a-repository
nvim-lspconf or nvim-lsp-configs since there are several.
The sooner the better.
Changed my mind again (x2): I am thinking:
neovim/nvim-lspconfig lspconfigconfigs singleton lives instead of wherever it lives right now.lua/lsp/configs/*.luaI didn't look closely, but it seems like there is no reason for nvim_lsp.lua to be a separate module. It should just be lua/lsp/configs.lua module.
agreed, the split looks a bit artificial and forces to submit changes across the 2 repo. Having really just the configs here would be best.
@h-michael do you feel like tackling https://github.com/neovim/nvim-lsp/issues/97#issuecomment-583717327 ?
@teto I'll try this this weekend.
Repo is now renamed from neovim/nvim-lsp to neovim/nvim-lspconfig .
Haven't done any code changes yet. Planning to rename the Lua module to lspconfig. This clearly distinguishes it from lsp while staying simple. see https://github.com/neovim/nvim-lsp/issues/97#issuecomment-583717327
Most helpful comment
@norcalli
It automsticaly redirects.
https://help.github.com/en/github/administering-a-repository/renaming-a-repository