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

Moving up/down follows neither visual or actual column now #44878

Closed
octref opened this issue Mar 2, 2018 · 7 comments
Closed

Moving up/down follows neither visual or actual column now #44878

octref opened this issue Mar 2, 2018 · 7 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@octref
Copy link
Contributor

octref commented Mar 2, 2018

Issue: #22717
PR: #44259

The PR does not fix the issue and introduced more issues.

Repro

Have the following text:

一二三四五六七八九十
	一二12345678901234567890 // tab in beginning
一二三四五六七八九十
1234567890123456789
  • Set font to Inconsolata
  • Set tabWidth to 4
  • Put cursor in last line after 1234. Now status bar col shows 5`
  • Up arrow
  • Now cursor is after 一二三四 and status bar col shows 9
  • 🐛 The cursor is NOT visually aligned with previous col position
    • If it works correctly, cursor should be after 一二
  • Regardless, you go up again
  • Now cursor is after 一二1 and status bar col shows 10
  • 🐛 The cursor is NOT visually aligned and NOT column-wise aligned with previous col position.
    • If it's visually aligned moving, you should end up after 一二 since 4x Chinese char are 8 spaces, and 1x tab + 2x Chinese char are also 8 spaces
    • If it's column aligned moving, you should end up after the initial tab since you have 4x Chinese char and tabWidth is 4.
@octref octref added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority editor labels Mar 2, 2018
@octref octref added this to the February 2018 milestone Mar 2, 2018
@alexdima
Copy link
Member

alexdima commented Mar 2, 2018

@octref Thank you for verifying, but I believe you have attempted to verify in a build that did not contain the fix (i.e. the behaviour you describe sounds a lot like what is on stable):

kapture 2018-03-02 at 9 32 29

@alexdima alexdima closed this as completed Mar 2, 2018
@octref
Copy link
Contributor Author

octref commented Mar 2, 2018

@alexandrudima I verified by building on commit ba38492 which has your fix 13 hours ago.

@alexdima
Copy link
Member

alexdima commented Mar 2, 2018

@octref Hmm...
What am I doing differently? Can you reproduce in today's insiders ?

@octref
Copy link
Contributor Author

octref commented Mar 2, 2018

And on the freshly built insiders too with d7dca14

edit

@alexdima
Copy link
Member

alexdima commented Mar 2, 2018

We chatted and the issue turned out to be with the vim extension.

@octref
Copy link
Contributor Author

octref commented Mar 2, 2018

@rebornix Think we should let VSCodeVim know so the new release wouldn't break for Chinese/Japanese Vim users.

@alexdima alexdima added invalid Issue identified as not relevant or not valid and removed invalid Issue identified as not relevant or not valid labels Mar 2, 2018
@octref octref added the verified Verification succeeded label Mar 3, 2018
@octref
Copy link
Contributor Author

octref commented Mar 3, 2018

This is working correctly in VS Code. Vim issue is tracked in #44958.

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants