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 position incorrect #80170

Closed
NanerLee opened this issue Sep 1, 2019 · 8 comments
Closed

cursor position incorrect #80170

NanerLee opened this issue Sep 1, 2019 · 8 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug editor-rendering Editor rendering issues font-rendering Font rendering issues linux Issues with VS Code on Linux

Comments

@NanerLee
Copy link

NanerLee commented Sep 1, 2019

  • VSCode Version: 1.37.1
  • OS Version: ubuntu lts 18.04.3

Steps to Reproduce:

Set "editor.renderWhitespace": "all" for watching easily

  1. open a new file
  2. press space key
    1
  3. press space key
    2
  4. press space key
    3
  5. press space key
    4

we can find the cursor position is incorrect

More info:

  1. I has three PCs, their are all ubuntu 18.04.3, but only one is normal.
  2. The bug may be not about vscode version. I tried some old version , the bug is still.

Does this issue occur when all extensions are disabled?: Yes

@alexdima
Copy link
Member

alexdima commented Sep 7, 2019

Workaround: "editor.disableMonospaceOptimizations": true

@alexdima alexdima added bug Issue identified by VS Code Team member as probable bug editor-rendering Editor rendering issues font-rendering Font rendering issues labels Sep 7, 2019
@NanerLee
Copy link
Author

NanerLee commented Sep 8, 2019

@alexandrudima it doesn't work. And vscode tell me it is a Unknown configuration setting
2019-09-08 11-26-45 的屏幕截图

@Talden
Copy link

Talden commented Sep 8, 2019

Can confirm the same bug on VS Code: 1.37.1 (from Microsofts repo) with Debian Stretch.

Sometimes the editor starts fine, sometimes not. But even successful starts can fail calculating metrics (maybe a font loading race).

@kaseiwang
Copy link

Workaround: "editor.disableMonospaceOptimizations": true

works on code(1.38.0-1) from archlinux/[community], thanks!

@Talden
Copy link

Talden commented Sep 9, 2019

Workaround: "editor.disableMonospaceOptimizations": true

works on code(1.38.0-1) from archlinux/[community], thanks!

Is it expected that the setting is reported as "Unknown Configuration Setting"? This is the case for this version (which isn't impacted by the defect):

Version: 1.38.0 (user setup)
Commit: 3db7e09
Date: 2019-09-03T21:49:13.459Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

@alexdima
Copy link
Member

Yes, currently this setting is for troubleshooting only, so it is normal for "editor.disableMonospaceOptimizations" to be unknown. In a perfect world the monospace optimizations should work and we wouldn't need this setting to turn it off. That's why I marked this as a bug as something is definitely no longer working...

@Rock718
Copy link

Rock718 commented Sep 10, 2019

Change vscode default fonts maybe useful.See #80210

@NanerLee
Copy link
Author

@Rock718 Thanks a lot, I change the default fonts to Noto Mono, it works!. And
editor.disableMonospaceOptimizations is not necessary

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 25, 2019
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 editor-rendering Editor rendering issues font-rendering Font rendering issues linux Issues with VS Code on Linux
Projects
None yet
Development

No branches or pull requests

5 participants