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

Cursor moves out of visible window area #15

Closed
andycraig opened this issue Nov 19, 2019 · 6 comments
Closed

Cursor moves out of visible window area #15

andycraig opened this issue Nov 19, 2019 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@andycraig
Copy link

Thank you very much for making this and putting it on the marketplace!

I've found that when in normal mode, moving the cursor off the top or bottom of the window does not cause the window to scroll.

To reproduce:

  1. Have enough text in the file that the bottom of the file cannot be seen
  2. Be in normal mode (not insert mode)
  3. Keep pressing j until the cursor moves below the last visible line
  4. Observe that the window does not scroll, and the cursor is no longer visible

The same applies when the top of the file is not visible and I move the cursor to the start of the file using gg.

I've disabled all extensions except Dance.

I've observed the issue on Linux and Windows.

Version info (Linux):

Dance: 0.1.4
Ubuntu 18.04.2 LTS
VSCode:
Version: 1.39.2
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:33:40.634Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.15.0-70-generic

Thank you, and let me know if there's any other info I can provide etc.!

@timjs
Copy link

timjs commented Nov 19, 2019

Heaving the same issue here.

@71 71 self-assigned this Nov 19, 2019
@71 71 added the bug Something isn't working label Nov 19, 2019
@71
Copy link
Owner

71 commented Nov 19, 2019

I just realized that the whole move implementation (left, right, top, down) is broken in various other ways... I've started working on a fix but it's going to take some time. In any case, thanks for the report.

@andycraig
Copy link
Author

No problems, I look forward to the fix whenever it’s ready :) Thanks again for all your work on this!

@71
Copy link
Owner

71 commented Nov 19, 2019

Commit bb84bfd fixes movements to be the same as Kakoune's!

@71 71 closed this as completed Nov 19, 2019
@andycraig
Copy link
Author

Wow, that was a lot quicker than I expected! Thank you!

@timjs
Copy link

timjs commented Nov 20, 2019

This still happens when using goto commands like gg or ge, when using the new n or a+n searches or just using search itself / or a+/!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants