Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vim extension causes cursor to jump when moving between multiple windows of the same file. #3064

Closed
Maelstorm1973 opened this issue Sep 21, 2018 · 1 comment

Comments

@Maelstorm1973
Copy link

Describe the bug
A clear and concise description of what the bug is.

When a file is open in two or more windows, the user clicks from one window to the next, then moving the cursor or typing in the window causes the cursor to jump to the same location that the cursor is in the previous window.

For example, when copying and pasting text from one window to another in the same file (common in software development), selecting and copying the text in the source window sets the cursor position at one point. Then when the attempt is made to paste, type, or move the cursor in the target window, the cursor will jump to the same location as the cursor in the source window.

To Reproduce
Steps to reproduce the behavior:

  1. Open a file in two different windows.
  2. Select text in one window (or just click somewhere).
  3. Move to the other window and move the cursor, type, etc....
  4. The cursor will jump to the same location as in the first window.

Expected behavior
A clear and concise description of what you expected to happen.

The cursor location in the second window should not change to match the cursor location in the first window.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 0.16.5
  • VSCode version: 1.27.2
  • OS: Windows 10 Pro x86-64

gas 0.0.1
PHP Debug 1.12.6
PHP Intelephense 0.8.8
PHP IntelliSense 2.3.5

Additional context
Add any other context about the problem here.

@jpoon
Copy link
Member

jpoon commented Sep 22, 2018

Closing as duplicate of #2688

@jpoon jpoon closed this as completed Sep 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants