3 ms·

According to the extension, ZLS is optional, but according to some zig docs I found, its part of the extension. I may have misread, I'll try this stuff again so

According to the extension, ZLS is optional, but according to some zig docs I found, its part of the extension. I may have misread, I'll try this stuff again sometime

brabel 2y ago
As with all VSCode language extensions, they will try to download and manage ZLS for you. That's ok if it's done well, but they probably have some ways to go still. I just prefer using Zig on emacs with the built-in eglot LSP client. You just tell it where you installed ZLS (and it won't do magic to get it for you) and off you go. It's the same level of support as with VS Code. If you're not new to emacs, maybe consider that (otherwise emacs may be too much of a rabbit hole :)).
- voidUpdate 2y ago
  My terminal editor of choice is nano :P
  - MobiusHorizons 2y ago
    It sounds like you have two editors at least, vscode and nano. Based on this description, I would assume you use nano for commit messages, config file updates, and not much more. If that’s the case, you may want to at least check out what emacs or vim can do for you with some basic lsp integration. These would be replacements for vscode not nano, although once you get used to them, you might switch EDITOR over. Compared to the complexity of systems programming, vim or eMacs should be well within your grasp.
    - voidUpdate 2y ago
      My terminal editor of choice is nano. I do quite a bit of document writing, programming, config file updating etc in nano when I'm on a system without a GUI, but if I'm on something with a proper GUI, I tend to use VSC for script writing. I've attempted to use vim before but the different modes and all the key combinations and shortcuts went in one ear and out the other. I barely remember how to exit. Nano has always just seemed more friendly to me, like "oh you want to write a file? Here's a text buffer, ctrl+x when you're done with it"

According to the extension, ZLS is optional, but according to some zig docs I found, its part of the extension. I may have misread, I'll try this stuff again sometime

brabel 2y ago

As with all VSCode language extensions, they will try to download and manage ZLS for you. That's ok if it's done well, but they probably have some ways to go still. I just prefer using Zig on emacs with the built-in eglot LSP client. You just tell it where you installed ZLS (and it won't do magic to get it for you) and off you go. It's the same level of support as with VS Code. If you're not new to emacs, maybe consider that (otherwise emacs may be too much of a rabbit hole :)).

voidUpdate 2y ago
My terminal editor of choice is nano :P
- MobiusHorizons 2y ago
  It sounds like you have two editors at least, vscode and nano. Based on this description, I would assume you use nano for commit messages, config file updates, and not much more. If that’s the case, you may want to at least check out what emacs or vim can do for you with some basic lsp integration. These would be replacements for vscode not nano, although once you get used to them, you might switch EDITOR over. Compared to the complexity of systems programming, vim or eMacs should be well within your grasp.
  - voidUpdate 2y ago
    My terminal editor of choice is nano. I do quite a bit of document writing, programming, config file updating etc in nano when I'm on a system without a GUI, but if I'm on something with a proper GUI, I tend to use VSC for script writing. I've attempted to use vim before but the different modes and all the key combinations and shortcuts went in one ear and out the other. I barely remember how to exit. Nano has always just seemed more friendly to me, like "oh you want to write a file? Here's a text buffer, ctrl+x when you're done with it"