| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The name `server_configurations` is extremely verbose and irritatingly
formal and dogmatic. This overlong name is a constant nuisance when
reading, writing, and coding.
It's also not even correct: these configurations are just as much
"client" configurations as they are "server" configurations.
Solution:
- Rename to a shorter name.
- Leave placeholder files for any old URLs that link to the old
location.
|
| | |
|
| |
|
|
|
| |
* fix: Follow latest denols implmention
* fix: Query clients with bufnr
|
| |
|
|
|
| |
* feat(denols): follow the latest default value of the vscode extension
* fix(denols): nvim_buf_set_option is deprecated
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
* feat: make deno/cache async
* feat: show file name in deno cache error
* fix: use fname isntead of uri
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I found the root cause of denols problems:
https://github.com/neovim/neovim/pull/19797
With that pr applied (and with this revert) denols works perfectly
almost identical to vscode deno, its missing some features but I imagine
those are out of scope for lspconfig.
Problems will reappear until nvim fixes:
https://github.com/neovim/nvim-lspconfig/issues/1998
This is an ok tradeoff because `single_file_support=true`
causes other issues:
https://github.com/neovim/nvim-lspconfig/issues/2069
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- remove unneeded lsp attach
- default to single_file_support=true
fix https://github.com/neovim/nvim-lspconfig/issues/1998
|
| |
|
|
| |
Caching actually works but it throws an error, vscode-deno also doesn't seem to care about errors
https://github.com/denoland/vscode_deno/blob/196a11cead2d95c324cb772dd568ba7c2801b68a/client/src/commands.ts#L60
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If you open a file and immediately try to go to definition this error happens:
```
{["error"]={["message"]="Method not found: deno/virtualTextDocument",["code"]="-32601"}}
{["error"]={["message"]="Method not found: deno/virtualTextDocument",["code"]="-32601"}}
{["error"]={["code"]="-32601",["message"]="Method not found: deno/virtualTextDocument"}}
{["error"]={["code"]="-32601",["message"]="Method not found: deno/virtualTextDocument"}}
```
Seems to be a race condition where the virtual text handling is not ready yet.
Because this error is unhelpful and the gotodefinition works normally after
a couple of seconds, just ignore it.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Linting is now enabled by default https://deno.com/blog/v1.22#linting-enabled-by-default-in-the-lsp
so it should not be turned off in these settings
- `tsconfig` is an outdated way to make any config changes in Deno and should not be used:
https://deno.land/manual/typescript/configuration#configuring-typescript-in-deno
> ⚠️ Deno v1.14 started supporting a more general configuration file that is no
> longer confined to specifying TypeScript compiler settings. Using
> tsconfig.json as a file name will still work, but we recommend to use
> deno.json or deno.jsonc
@jason0x43 agreed in the previous thread:
https://github.com/neovim/nvim-lspconfig/pull/1321#issuecomment-1024191242
> Currently, deno only looks for deno.json, deno.jsonc, tsconfig.json, or .git
> to determine the root. I think dropping tsconfig.json makes sense because Deno
> now has it's own preferred config file name. Having .git seems reasonable
> enough because projects will often be in git repos. I could even see enabling
> single_file mode by default for the Deno LS since making simple CLI tools is
> (theoretically) a standard use case.
If this pull request is accepted then the docs can also be simplified:
https://deno.land/manual/getting_started/setup_your_environment#neovim-06-and-nvim-lspconfig
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
