ZLS has dropped the latest stable version with 0.15 support.
From vscode extension: Failed to install ZLS 0.15.0. Not Found (404)
I also have the binary with zls.exe.
Is there some way to bypass this vscode extension manager? It fails all the time.
You should be able to specify the zig/zls paths manually in the extension settings.
Finally! Thanks! After many hours of fiddling.
I can NAVIGATE again ![]()
hi, I’m using neovim (no changes with kickstart so lazy+nvim.lspconfig) and I built zls from source, specified absolute path to bin, checked many times zls --version
yet, in :checkhealth vim.lsp says
vim.lsp: Active Clients ~
- zls (id: 1)
- Version: 0.14.0
and I assume it’s why it says it can’t resolve standard library directory
anyone got an insight on this?
EDIT : its mason using it’s own downloaded zls… I gotta force it to append to PATH so mine takes priority
I feel this so much. I got my start programming back in the early 00’s when Ruby was hot and it was the scripting language used for RPG Maker XP. At the time the only thing I used to write code was the built-in editor of RPG Maker, whose only “code editor” functionality was very basic syntax highlighting, and I had no problem whatsoever. Fast forward 20 years, and with all of the experience I have gained since then, I find myself nearly crippled without a functioning LSP, which makes me feel kind of sad…
Navigating / programming with a notepad experience is possible but very time consuming
But good for your memory!!
I wasn’t expecting myself to pick up the good old working style of programming to a lot of manual pages and running compilers from time to time to fix trivial syntax errors.
Good flashback tbh but I’d never live in the old days again ![]()
So much so great appreciation goes to the excellent ZLS team. It’s really great to see how much the Zig ecosystem stresses on basic tooling. It really makes a difference.
It makes me realize how spoiled I have gotten and how sloppy LSP’s have made my typing when I write code. My brain is trained to just start typing a few keystrokes and tabbing for auto-complete, where I don’t even concern myself with accuracy, as the fuzzy-finder gets me there when it is “close enough”. It is akin to those who frequently use an LLM will still briefly pause to wait for the LLM auto-complete even when not using it: it just becomes muscle memory and requires additional focus when it is not present.
Sometimes ZLS is out of sync with the sourcecode, althoug I already saved the file. Like:
- Jumping to the wrong line (jump to declaration).
- not highlighting an imported function correctly.
What is a good strategy too sync it again?
I am personally not able to reproduce that behavior with neovim, whether it is saved to disk or recent modifications that exist only an unsaved buffer, it is still jumping to the correct location.
Could it be something vscode related, such as an outdated cache?
I don’t know what is the cause.
All I know is: all files are safed, i also executed a zig build.
Restarting vscode solves the problem.
Is ZLS dependent on CodeLLDB? That one is gone (debugging is impossible anyway).
I did not have the problem before I think.
EDIT: zig.zls.startRestart in the command palette also solves it.
That is a bit strange since the LSP protocol doesn’t need your files to be saved to work.