Chris Grieser

The same seems to apply to `append()`, `indent()`, and `setline()`. `line()`, however, seems to correctly accept strings like `"."`

I was also surprised that the de-facto standard-linter for CSS was not included, and would support the request. Just to add, there is also the very common stylelint plugin [stylelint-order](https://github.com/hudochenkov/stylelint-order),...

As I said, `eslint_d` works for `null-ls`, but not for the eslint-lsp

Hmm, that's really a bummer, being able to manage all linters and formatters via Mason, expect one 😕 Maybe it would work via symlinking the eslint binary to whatever location...

okay, I just tried installing `eslint_d` via Mason, and symlinking to the location where `npm -g eslint` would install `eslint` to normally: ```bash ln -sf $HOME/.local/share/nvim/mason/packages/eslint_d/node_modules/eslint_d /opt/homebrew/lib/node_modules/eslint ``` Unfortunately, this...

hah, that was the needed stepstone. So I installed `eslint` in the location it would be installed if available via Mason. In my case on mac: ```bash cd "$HOME/.local/share/nvim/mason/packages" mkdir...

I can confirm the issue. It's tricky, the LSP simply does not work, and only after going through `:LspLog` the underlying issue becomes apparent, making it hard for beginners to...

Ok, so I looked into it, and the root cause is these lines in the mason-registry repo: https://github.com/chrisgrieser/mason-registry/blob/main/packages/ltex-ls/package.yaml#L17-L34 it only lists the ltex-cli and lsp, but not the jdk bundled...

**edit:** the PR has been merged, making all the instructions below obsolete. Just uninstall and install via mason, wait for the download to finish (might take a bit, because the...

When you say UI issue, do you mean display issue? Because unfortunately, it is not just a display issue. The packages can't be run as LSP servers, and the linter/formatters...