| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
idk how to make this error stop
though I did read: https://github.com/EmmyLuaLs/emmylua-analyzer-rust/issues/29
error: undefined global variable: vim [undefined-global]
--> lua/lspconfig/configs/taplo.lua:6:29
5 | root_dir = function(fname)
6 | return vim.fs.dirname(vim.fs.find('.git', { path = fname, upward = true })[1])
7 | end,
|
| |/
|
|
|
|
| |
- Introduce emmylua CI job to type-check code.
- Drop old analyzers that haven't reported anything useful in a long
time and are redundant with luals/emmylua.
|
| |
|
|
|
|
|
| |
Problem:
`config.root` is not a valid field.
Solution
Replace it by `config.root_dir`.
|
| |
|
|
|
|
|
|
|
|
|
| |
Problem:
Neovim not finding slangd when installed via Mason on Windows
eventhough running :!slangd is fine.
No error if included in PATH
Solution:
Use slangd instead of slangd.exe even on windows.
This allows Neovim to find slangd when installed via Mason or
manually by adding to PATH
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
| |
Close https://github.com/neovim/nvim-lspconfig/issues/4129
Since cwd is a necessity for many JavaScript project (see discussions in https://github.com/neovim/nvim-lspconfig/issues/4015), this fix takes an alternative approach to manually exclude Deno projects from biome/eslint/ts_ls/tsgo/vtsls 's `root_dir` detection logic. There is no need to change svelte since it has a different filetype.
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
| |
The cmd function's config parameter can sometimes be nil,
causing a warning when attempting to access config.root.
Added a nil check to safely handle this case.
Fixes #4180
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
| |
See: https://github.com/elixir-lang/expert/issues/193#issuecomment-3480787095
Fix tested locally
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The various `tinymist` export commands like `LspTinymistExportPdf` used
to output simple path strings. With the release of `v0.13.30` the output
is now a structure like `{ path = "..." }`. Other export commands have
slightly different outputs. Calling `vim.notify` with this input leads
to `Error executing vim.schedule lua callback: vim/_editor.lua:0: ...`.
Solution:
Pass the result of all commands to `vim.inspect`.
Update the list of workspace commands in the brief.
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The current config for Angular LS make strong assumptions when trying to
find the root dir, which can lead to unexpected LSP crashes.
Solution:
By defining the 'cmd' field as a function, the config employs Neovim's
LSP root resolution to identify the correct path and find the relevant
node_modules folder.
Co-authored-by: Erikson Kaszubowski <erikson.kaszubowski@serpro.gov.br>
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
**Problem**: When working in a python monorepo with a base `pyproject.toml`, and `pyrightconfig.json` files that extend this base configuration in subdirectories, `pyright` will not recognize these `pyrightconfig.json` and identify these subdirectories (project1 | project2) as root directories because `pyproject.toml` takes precedence.
```sh
# Example structure
monorepo
├── project1
│ ├── pyrightconfig.json
│ └── src
│ └── main.py
├── project2
│ ├── pyrightconfig.json
│ └── src
│ └── main.py
└── pyproject.toml
```
From the pyright docs [1]
> A “pyrightconfig.json” file always takes precedent over “pyproject.toml” if both are present
**Solution**: Update the order of the `root_markers` to prefer `pyrightconfig.json` so priority is in line with pyrights documentation.
**Testing**: When creating a simple monorepo structure with the following command
```sh
mkdir monorepo && touch monorepo/pyproject.toml && mkdir monorepo/project1 && touch monorepo/project1/pyrightconfig.json && mkdir monorepo/project1/src && touch monorepo/project1/src/main.py && cp -r monorepo/project1 monorepo/project2
```
You should be able to open one of the subdirectories `nvim monorepo/project1/src/main.py` and check your LSP root dir with `:LspInfo`, and it should be attached to the subdirectory.
1. https://github.com/microsoft/pyright/blob/main/docs/configuration.md#pyright-configuration
|
| |
|
|
| |
skip-checks: true
|
| |
|
| |
Set `cmd_cwd=root_dir` at launch-time, instead of manually trying to guess a CWD.
|
| |
|
|
|
|
|
|
|
| |
Problem:
The `root_dir()` function for `termux_language_server`
introduced in #4161 calls `on_dir()` unconditionally.
Leading to `termux_language_server` attaching to all buffers.
Solution:
Make the call conditional.
|
| |
|
|
|
|
|
|
| |
Currently csharp-language-server starts to find solution file or project file from current directly, and just ignore rootPath and rootUri as metioned in razzmatazz/csharp-language-server#272.
Also, legacy style of configuration[ set cmd_cwd to root_dir](https://github.com/neovim/nvim-lspconfig/blob/2b52bc2190c8efde2e4de02d829a138666774c7c/lua/lspconfig/manager.lua#L118-L120), but not currently.
So, as mentioned in #3849, the server cannot find solution file or project file as the server is launched in cwd not in the directory root_dir find out.
This problem will be solved in future version of language server, but I think it would be better to set cmd_cwd the place same as root_dir, as currently it's one solution for this problem, and in future, it will help users who using old version of server.
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
| |
Codelens requires a bit of special configuration to work on rust-analyzer as described here:
neovim/neovim#34353 (comment)
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem:
`termux_language_server`'s `filetypes` field
is set to the non-existent `PKGBUILD` filetype,
thus the LSP never attaches to a target buffer.
Solution:
Replace the `filetypes` field with a `root_dir`
function matching the filename pattern suggested
by upstream.
https://termux-language-server.readthedocs.io/en/latest/resources/configure.html#neovim
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
| |
Update references from postgrestools to postgres-language-server following
the project's renaming. This includes the command, documentation URL, and
root markers.
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
| |
According to https://github.com/julia-vscode/LanguageServer.jl/issues/1366
, we need SymbolServer and StaticLint on the latest commits.
|
| |
|
|
| |
skip-checks: true
|
| | |
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Some servers don't stop properly.
Calling `:LspStop` _twice_ will induce a force-stop, but that is not easy to
discover: https://github.com/neovim/neovim/blob/b67eff38fe19876ab228007897224ec04b58aa40/runtime/lua/vim/lsp/client.lua#L864-L866
> By default, it will just request the server to shutdown without force. If
> you request to stop a client which has previously been requested to
> shutdown, it will automatically escalate and force shutdown.
Solution:
Nvim should automatically force-stop after X seconds, but until that is
supported, adding a bang "!" variant is reasonable.
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
| |
settings.gradle is marker for multi-module Gradle projects.
See: https://docs.gradle.org/current/userguide/multi_project_builds.html
Closes: #4137
Signed-off-by: Tomas Slusny <slusnucky@gmail.com>
|
| |
|
|
| |
skip-checks: true
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Root directory is incorrect for projects containing a `package.json` file in subdirectories.
For a project with a given file structure:
```
my-monorepo/
├── package.json
├── yarn.lock
├── css/
│ └── css-variables/
│ ├── color.css
│ └── typography.css
└── components/
└── core/
└── my-feature/
├── package.json ← 2. causes LSP root to stop here
├── feature-component-a/
│ └── feature-component-a.module.css ← 1. current open buffer
└── feature-component-b/
└── feature-component-b.module.css
```
The LSP is using `my-feature` as the root directory. This directory is not the one where the css variables are defined. It leads to an issue where the css variables are not indexed, and from `feature-component-a.module.css` auto-completion and jump to definition are not working.
Solution:
Using the same `root_dir` logic as `ts_ls` (which prefers lockfiles like yarn.lock or .git as root markers) correctly sets the project root to `my-monorepo/`, allowing `css/css-variables/` to be discoverable for the LSP.
|
