Luasnip - After using snippets, tab key press triggers unexpected cursor jumps

[jorgealbertowork]

Before Reporting an Issue

• I have read the kickstart.nvim README.md.

• I have read the appropriate plugin's documentation.

• I have searched that this issue has not been reported before.

• By checking this, I confirm that the above steps are completed. I understand leaving this unchecked will result in this report being closed immediately.

Describe the bug

Appears to be the same one described here: #302

Although reported before in a now closed issue, I believe this has never been fixed.

After using any snippet, when I turn back to inserting text manually, using the tab key to indent code will trigger an unexpected jump to the last snippet used.

To Reproduce

1. Use any snippet.
2. After editing the snippet, try to insert text in a new line
3. Use the tab key to add indentation on new line, cursor jumps unexpectedly to the last snippet location.

Desktop

• OS: Linux Mint
• Terminal: XFCE4-Terminal

Neovim Version

NVIM v0.11.3                                                                                                           
Build type: Release                                                                                                    
LuaJIT 2.1.1741730670  

[onur-tlntmr]

I can reproduce this issue.
Can someone help ?

Desktop:

• Fedora 42
• Gnome Terminal 48.5

NVIM v0.11.4
BuildType: RelWithDebInfo
LuaJIT 2.1.1748459687

[wumtdev]

Just add this wherever you want in init.lua:

vim.api.nvim_create_autocmd('ModeChanged', {
  command = 'LuaSnipUnlinkCurrent',
  desc = "Close code snippet editing after insert mode exit, so <Tab> won't unexpectedly jump back to it",
  pattern = 'i:*',
})