bug: Attempt to index field 'foldupdate_range' (a nil value) about lazyvim

[tomtomjhj]

Here's the scenario that I guess you were running into.

1. In insert mode, do some edits that update the syntax tree.
2. Leave insert mode with ctrl-c.
3. Make edits in normal mode that update the syntax tree. This happens to be the change made by code_action.
4. Enter insert mode, and leave insert mode with ESC, without making changes.
5. nil error

I have fixed this and explained why this happens in neovim/neovim#29581

[s1n7ax]

@tomtomjhj of course dafuq was I thinking XD

[folke]

Looks like a Neovim bug

[tomtomjhj]

the error message says that the error happened when processing bufwritepre, which means that nvim was saving the file and trigger auto formating (which isnt included in your repro steps). were you actually saving the file when this happened? can you reproduce this by doing some edits in insert mode and concurrently trigger auto formatting without leaving insert mode?

also, do you use ctrl-c to exit insert mode?

[kapral18]

@tomtomjhj

yes I do use mostly ctrl-c instead of esc as much as possible. Do you think it can affect this?

This happens randomly. For example this happens when I try to exit fzf-lua window when I am checking for lsp references and kill it with ctrl-c. But I noticed it mostly happens with list of new references that I haven't visited yet.

Or this happens when I try to complete the auto imports from normal mode with tsserver or typescript-tools add imports functionality with lsp code actions. And again happens with new imports mostly.

@tomtomjhj can you tell me how to trigger autoformatting without leaving insert mode?

[tomtomjhj]

yes I do use mostly ctrl-c instead of esc as much as possible. Do you think it can affect this?

yes this seems to be the root cause. leaving insert mode eith ctrl-c doesn't trigger insertleave autocmd, and this confuses treesitter fold stuff. i missed this point when i made changes to it.

the fix is simple: just add a nil check. i was initially hesitant to do this because it didnt seem necessary, but it turns out it's indeed necessary. i'll make pr soon.

[s1n7ax]

Can confirm this is happening in 0.11 as well. This occurs in Typescript, Lua, Java files.

Almost 70% time this occurs when I organize imports in Typescript files or use vim.lsp.buf.code_action() to import something. And then sometimes when I use Telescope.

[tomtomjhj]

@s1n7ax do you use ctrl-c to exit insert mode?

[kapral18]

this was definitely a ctrl-c issue in my case

[s1n7ax]

@tomtomjhj Yes but how is that related to error occurring when vim.lsp.buf.code_action() is used? Anyway, just added a remap for <c-c> to <esc>

[s1n7ax]

@tomtomjhj Ah. Cool. So far no errors with nmap <c-c> <esc>.

[s1n7ax]

nmap <c-c> <esc> don't fix the issue. Hopefully PR will be merged soon

[tomtomjhj]

inoremap <c-c> <esc>