How to display default settings set by zls itself? #1010
Replies: 2 comments 3 replies
-
You can find all config options and default values in the README. You will not find any options for controlling completions because you don't need to enable it.
If I understand you correctly you mean that if you start typing after an ZLS should already give you completions (including builtins) without having to enable certain config options. There could be something wrong with your current setup or there is a some issue with ZLS. Maybe we can find the problem if you answer the following questions to narrow down the issue:
BTW if your interested, we also have a discord server here where others may also help you out. How to open ZLS logs for some editorsMake sure that debug logs are enable when running ZLS by doing at least one of the following things:
The output should look similar to this: |
Beta Was this translation helpful? Give feedback.
-
Yes, I know about the
Yes, I expected it to work like the other auto-completion works without a problem.
This seems to work just fine, only the I expected it to offer me suggestions when I press the dot right after
That's also a plausible scenario.
Editor:
let g:completor_filetype_map = {}
let g:completor_filetype_map.zig = {'ft': 'lsp', 'cmd': 'zls'}
Yes, both of them are set correctly.
I don't use hover or goto; semantic highlighting seems to work just fine, I haven't witnessed any problematic behavior so far.
OK, I will add the flag in my mapped settings and let you know. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately this is a known limitation of ZLS, you should instead assign it to constant and then use it like this: const std = @import("std");
fn foo() void {
std. // <- right here
}
I've just setup Vim with the configuration you have given me. Completions on builtins also didn't work for me like this example: const std = @import("std");
fn foo() void {
@ // <- start typing import so that it should show completions
}Looking at the response ZLS sends to completor thanks to It would be possible to file a bug report against |
Beta Was this translation helpful? Give feedback.
-
Yeah, this works as expected. Food for thoughtWhat is the actual scope for The reason I'm asking is because I thought it could be handy to create a temporary (hidden from user) variable in the same scope category as a local variable that we use to assign either the entire...what is called, module or namespace? I'm currently learning Zig, so be gentle here 😆 As I was saying, something like an expansion mechanism to allow the autocompletion mechanism to kick in (get triggered?).
If you try
I have already opened a ticket, see below.
I have tried both of them; YouCompleteMe is a beast comparing Anyway, I will continue using it, even with this minor obstacle, but I'm quite pleased by it. There are some problems with it from time to time with autocompletion that is, but I will figure things out. If they are bugs, I'm sure they will get repaired soon and released as bugfixes. |
Beta Was this translation helpful? Give feedback.
-
|
The only debug output I could produce was the one I don't know how much it helps, but I have asked the plugin creator how to log LSP's output: maralla/completor.vim#321 I guess I will have to wait until I get an answer. |
Beta Was this translation helpful? Give feedback.
-
zls --show-config-pathshows/home/stefanos/.config/zls.json, but when I go there to open the file, I can see it does not exist.How can I find the default settings set up by zls itself?
Basically I want to make it autocomplete or offer suggestions on
@insertion.Beta Was this translation helpful? Give feedback.
All reactions