Vim: <c-o>/<c-t> jump back to wrong location after 'gd'
Describe the bug
Pressing
Re-reporting #3277 since this bug has not been re-introduced (I'm guessing after the 1s sleep was removed)
To Reproduce
Press 'gd'
Press
Now in wrong location
Expected behavior
Going to the previous location
Environment (please complete the following information):
- Extension (VsCodeVim) version: 1.12.4
- VSCode version: 1.41.1
- OS: macOS 10.14.6
Additional context
Add any other context about the problem here.
drewthor
All 5 comments
Duplicate of #4470. I'm pretty sure you're right that this broke after I removed the timeout. Maybe we can get around that, or maybe I need to add it back in a more limited context.
J-Fields
on 8 Jan 2020
Workaround: https://github.com/VSCodeVim/Vim/issues/3277#issuecomment-577780535
troygibb
on 23 Jan 2020
Workaround: #3277 (comment)
@troygibb does this work for you as intended? In my case, it seems that Vim extension hijacks VSCode's Go back stack, so if I do gd and then jjjjjjj, Go back brings me to the previous line instead of the file I jump from.
As for C-o it seems broken on all 1.12.x - I got reasonable behaviour only with 1.11.3.
artempyanykh
on 23 Jan 2020
May I ask are there any fixes or updates?
yyn19951228
on 13 Feb 2020
This issue seems exacerbated when you open more than one file, especially if you have more than one file open in window splits (:vsp for example.) I find that the ctrl-t, ctrl-o works decently with just one window/tab open, but obviously that is a severely limiting restriction. Hopefully, that gives a hint as to what might be going wrong.
Just to add my two-cents: bugs like this make VSCodeVim pretty unusable to the point I just want to turn it off, and/or just stick to vim or qtcreator (which has a half decent FakeVim implementation.) As such, I'd place this at "priority level: do or die", that is I see the future of this plugin decided by the presence (or lack of) a robust resolution to this bug.
mattgara
on 14 Feb 2020
Related issues
gerardmrk
路
3Comments
rajinder-yadav
路
3Comments
typeoneerror
路
3Comments
jaredly
路
3Comments
elithrar
路
3Comments
Most helpful comment
This issue seems exacerbated when you open more than one file, especially if you have more than one file open in window splits (:vsp for example.) I find that the ctrl-t, ctrl-o works decently with just one window/tab open, but obviously that is a severely limiting restriction. Hopefully, that gives a hint as to what might be going wrong.
Just to add my two-cents: bugs like this make VSCodeVim pretty unusable to the point I just want to turn it off, and/or just stick to vim or qtcreator (which has a half decent FakeVim implementation.) As such, I'd place this at "priority level: do or die", that is I see the future of this plugin decided by the presence (or lack of) a robust resolution to this bug.