Using 'n' ends up searching for the last searched term and thus moving the cursor

[lokesh-krishna]

Whenever I use n as part of the default keybinds, my cursor usually ends up jumping around as it triggers searching for the next instance of the last searched term. I'm sure I'm missing some fairly obvious workaround here but could someone please be patient enough to point out what it might be?

[gegoune]

This is default vim/nvim's mapping. What do you expect to happen instead?

[lokesh-krishna]

A way to disable it in the nvim-tree buffer? How does one handle the cursor jumping around. I hit na to create a new file at one place but the n moves the cursor elsewhere and I get the prompt to create the file at a different location than the one I intended.

[gegoune]

Why do you press n for exactly? It does what is suppose to do, go to next match of last searched pattern.

[lokesh-krishna]

Um, the keybind to create a new file is na, right? So when I'm pressing n for that is when I don't want it to move to the next match.

[gegoune]

No, it's not, it's just a by default. Are you mistaking n from vim.keymap.set's first argument (which is mode, see :h vim.keymap.set) with actual mapping?

In short, just use a. n is for normal mode.

[lokesh-krishna]

Wow, I feel stupid. Thanks for being so patient!