-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zM
and zR
sometimes do change foldlevel
(nvchad config)
#206
Comments
I will try reducing the core config later and hopefully will see what is causing the issue. |
It looks like this is the culprit: opt.timeoutlen = 400
-- Time in milliseconds to wait for a mapped sequence to complete (default 1000). It looks like I'm not sure, but it probably has something to do with which key and how quickly I need to execute a keymap. Yeah, I changed it between |
Nope, for |
Find the culprit plugin first. |
I have this same behavior in my nvim config started from kickstart.nvim. Removing nvim-ufo removes the zM behavior although this could be a plugin interaction. Strangely, when I bind zm (lowercase) to closeFoldsWith(1), typing it with a delay sets the foldlevel to 98 (default 99). Will update when I have more time to make a minimal config demonstrating the issue. |
Neovim version (nvim -v | head -n1)
NVIM v0.9.4
Operating system/version
Pop!_OS 22.04
How to reproduce the issue
I tried using a lazy.nvim config:
config
for a bit, and it looks like everything is fine. But I'm using nvchad v2.0 and with its minimal config:
config
It sometimes/eventually does change the fold level. And the main problem is that I have no idea why this happens.
nvim-ufo.zip
Inside the container run
j
and then tryzM
and previously savedecho &foldlevel
which eventually will change to0
. If didn't change then exit and repeat (I didn't even save).Expected behavior
The
foldlevel
should always be the same after pressingzM
orzR
.Actual behavior
The value can change, which is seemingly random, but normally happens on the first or second try.
The text was updated successfully, but these errors were encountered: