Error with selecting snippet while writing in Go

[whughesiii2187]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.snippets

Question

I have seen this issue before but creator was unable to replicate. This time I have a recording for my receiving the error.
When coding in go, I am selecting a snippet and when I press Enter after tabbing to the selection I want, I get an error that I have recorded.

Error executing vim.schedule lua callback: ...vim/site/pack/deps/start/mini.nvim/lua/mini/snippets.lua:2345: Index out of bounds
stack traceback:
[C]: in function 'nvim_buf_get_text'
...vim/site/pack/deps/start/mini.nvim/lua/mini/snippets.lua:2345: in function 'session_sync_current_tabstop'
...vim/site/pack/deps/start/mini.nvim/lua/mini/snippets.lua:2139: in function 'session_init'
...vim/site/pack/deps/start/mini.nvim/lua/mini/snippets.lua:1339: in function 'call_in_insert_mode'
...vim/site/pack/deps/start/mini.nvim/lua/mini/snippets.lua:1337: in function 'insert'
...m/site/pack/deps/start/mini.nvim/lua/mini/completion.lua:1400: in function <...m/site/pack/deps/start/mini.nvim/lua/mini/
completion.lua:1350>

screenrecording-2025-11-30_15-09-11.mp4

[whughesiii2187]

I should add that this happens after having MiniMax opened for quite a while and exiting and entering again resolves it.

[echasnovski]

Thanks for the screencast!

I am afraid, the answer here is the same as #2118: I think it is because there was deviation from the expected snippet session lifecycle. Without exact steps for me to reproduce this when following snippet session lifecycle, there isn't much to do here. I'll take another look at the code, but there probably won't be anything new.

By the way, any reason why you didn't post it in #2118 directly? I'd expect it to be posted there, as the issue was closed until there is something new to add to the discussion.

[echasnovski]

I still think that this is an issue with not following the snippet session. So without the reproduction, I am going to close this.

There is now also e5a9a38 which would probably make this case at least not error.