The next release of `buf` will include LSP features that include support
for buf config files. This follows the approach that other LSPs follow
for specifying custom filetypes (a comment + adding that custom
filetype to filetypes).
Problem:
`find_tailwind_global_css` attempted to address #4204, where `experimental.configFile` was set using the return value of `vim.fs.find()`.
The language server rejected this with `Invalid experimental.configFile
configuration, not initializing` because `configFile` expects either a string or
a key-value record (object), not an array/list. This was a syntax issue, not
a detection issue.
Using the correct syntax for `configFile` in Lua should be
sufficient to address the original issue. Right now, `find_tailwind_global_css`
always runs for users who haven't explicitly set `configFile` — overriding the
LSP's native detection and **forcing anyone who wants to opt out to manually set
all entry-points by hand.**
Solution:
- Remove `find_tailwind_global_css` entirely and restores `configFile` to its
default `nil` so the `tailwindcss` LSP handles project detection natively.
- Simplify `before_init` based on [this suggestion from the initial
PR](https://github.com/neovim/nvim-lspconfig/pull/4222#discussion_r3018499628).
The following syntax worked for me while testing to explicitly set the
`configFile` based on the [official
docs](https://github.com/tailwindlabs/tailwindcss-intellisense#tailwindcssexperimentalconfigfile)
for single entry-point:
> [!NOTE]
> Single entry-point is resolved relative to the workspace root (`root_dir` — verify with `:checkhealth vim.lsp`)
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
-- v3: config file
configFile = 'tailwind.config.js',
-- v4: CSS entry-point
-- configFile = 'src/styles/app.css',
},
},
},
})
```
For projects with multiple entry-points, or different projects, the following
syntax can be used for multiple entry-points:
> [!NOTE]
> Keys are relative to `root_dir` as above, but from my testing on macOS, absolute paths worked better
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
configFile = {
['tailwind.config.js'] = '/Users/username/path/to/project-a/**',
['src/main.css'] = '/Users/username/path/to/project-b/**',
},
},
},
},
})
```
#### Project or Local Configuration
For project-specific settings without modifying your global Neovim config:
1. Enable in your Neovim config:
```lua
vim.o.exrc = true
```
2. Create `.nvim.lua` in the project root:
```lua
vim.lsp.config('tailwindcss', {
settings = {
tailwindCSS = {
experimental = {
configFile = 'tailwind.config.ts',
},
},
},
})
```
3. Open `.nvim.lua` and run `:trust` to allow the file, then restart Neovim.
4. Verify with `:checkhealth vim.lsp`.
Problem:
ci failure after previous change:
scripts/docgen.lua:249: attempt to index field 'version' (a function value)
Solution:
fix AI slop nooooo 😭 forgive me 🦞
Problem:
The docgen script makes unwanted noise changes like this:
diff --git a/doc/configs.md b/doc/configs.md
index 25e2bc71d1..d8822ef0f4 100644
--- a/doc/configs.md
+++ b/doc/configs.md
@@ -2481,11 +2481,11 @@ Default config:
{
editorInfo = {
name = "Neovim",
- version = "0.12.0-dev+gc9e961994b"
+ version = "0.12.0-dev+g925e9e8722"
},
editorPluginInfo = {
name = "Neovim",
- version = "0.12.0-dev+gc9e961994b"
+ version = "0.12.0-dev+g925e9e8722"
}
}
```
Solution:
During doc generation, patch vim.version to be less noisy.
Problem:
docgen fails if gen-annotations pushes before it:
[master c2804a4] docs: update configs.md skip-checks: true
2 files changed, 24 insertions(+), 20 deletions(-)
To https://github.com/neovim/nvim-lspconfig
! [rejected] master -> master (fetch first)
error: failed to push some refs to 'https://github.com/neovim/nvim-lspconfig'
hint: Updates were rejected because the remote contains work that you do not
hint: have locally. This is usually caused by another repository pushing to
Solution:
If push fails, rebase and retry. The two workflows touch disjoint files
so the rebase should alway resolve.
Problem: no LSP config exists for vimdoc (vim help) files.
Solution: add config for `vimdoc-language-server`, a language server
providing formatting, diagnostics, document symbols, and go-to-definition
for vimdoc files.
The current biome project root logic uses JS package manager
lockfiles to get the project root in mono repos.
If one is not using any JS (wasm) and raw CSS, that doesn't work out.
In those cases, only a biome.json exists as a marker on where the
frontend's project root inside the mono repo may be located.
Setting `offset_encoding` to `utf-8` is causing problem. See discussion at https://github.com/neovim/neovim/discussions/38375.
According to LSP specification 3.17, when `positionEncoding` is not specified in server capability, it's value should be assumed to be `utf-16`, see https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#serverCapabilities.
roslyn_ls does not response `positionEncoding` in initialize result (version `5.4.0-2.26162.5+e11fbc2bc8292680a92d731e5d9a6c7ee229262d`). One can verify this by setting LSP log level to debug, and read LSP log.
So, setting `offset_encoding` in default config is a mistake.
