Ctrl-o (go back) record every cursor move ?

[WangRongda]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE
What happened:
When I use 'gd' to go defined, it dump to another file, and press ctrl-o to go back.
But go back in vscode is based on step that record every cursor move and the history stack is limited.If I move many time, I could not go back to the last file.

What did you expect to happen:
Like the native vim: don't record every move or add new feature that support go-back-file-based.

How to reproduce it (as minimally and precisely as possible):

Environment:

• Extension (VsCodeVim) version:0.11.2
• VSCode version:1.12.1
• OS version:4.15.9-1-ARCH

[akirchhoff-modular]

Vim does record certain movements within a file as well, but not nearly so many as VSCodeVim erroneously does. The complete list of movements that cause an entry in the jump list consulted by CTRL-O is available in Vim's help, under jump-motions.

[WangRongda]

@alex-xnor
You are right!
I don't know how vim define a jumping, but It should not be a cursor move.

[jazmit]

+1 This is really annoying

[shawnaxsom]

Duplicate of #1933? I'm working on a potential solution. I'm tracking positions for any actions that occur within VSCodeVim, and then I'll look at also tracking some major external events like changing the editor or group. I'll then probably need to add a metadata tag on actions to specify whether they should be included in the jump list or not.

[akirchhoff-modular]

@axs221 Yes, I think this is a duplicate of #1933.

[jpoon]

Indeed it as a duplicate and closing it as such.