ocamlls was added at #76.
It was because ocaml-lsp-server, which is official one, was too young.
In 2025, the official one works fine. On the other hand, unofficial
ocaml-language-server is not maintaned. We can no longer access its
GitHub repository.
Issue: #4115
Problem:
If project had a nested child gitlab file named: .gitlab-ci.yml it would
take it as root.
Solution:
If inside GIT repository just use git repository root as root and still
keep the option for .gitlab* as fallback if there is no git repo yet.
Problem:
Installing the pug lsp using the suggested method (`go get github.com/opa-oz/pug-lsp`)
does not work in the latest versions of `go` and instead produces a
message the "'go get' is no longer supported outside a module".
Solution:
Change the install command for the pug lsp to the correct command which
is `go install github.com/opa-oz/pug-lsp@latest`.
Problem:
If a server is attached to a non-current buffer by
`vim.lsp.buf_attach_client`, then the Language Server-related
commands may be created in the current (wrong) buffer.
Solution:
Always use the `bufnr` arg provided to `on_attach`.
Enhance root directory detection for the latest versions of
TailwindCSS v4, which no longer require tailwind.config.* or
postcss.config.*.
For Phoenix projects, they are typically generated or add Tailwind
installed via https://github.com/phoenixframework/tailwind which will
now be detected by scanning the mix.lock file for the included package.
Phoenix projects that install tailwindcss via package.json should still
work.
This change was made because the current configuration (as of today) does not actually work. This new configuration addresses that issue by updating the cmd used for executing the lsp server. As well as updating the description to instruct users on how to install `rpm-spec-language-server`.
The escape_wildcards function was enhanced to handle a broader range of
special characters that could cause issues when used in pattern matching.
This includes additional wildcards, pattern matching characters, shell
special characters, the escape character itself, and whitespace.
This change provides more robust path handling throughout the codebase
when dealing with file paths that contain special characters.
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
The tblgen_lsp_server doesn't seem to load any specific compilation
database server and hence we need to explicitly specify the command-line
argument to pick the correct database path.