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

Insider integrated terminal cannot render underscore character properly #36862

Closed
tangorboyz opened this issue Oct 25, 2017 · 9 comments
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@tangorboyz
Copy link

  • VSCode Version: 1.18.0-insider commit: aaec298
  • OS Version: Ubuntu 16.04

This is both happen in light and dark theme

Steps to Reproduce:

  1. Launch VSCode and open integrated terminal
  2. Type underscore character and try to switch the vscode theme

image
I already type the underscore character but it doesn't appear.

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Oct 25, 2017
@tangorboyz
Copy link
Author

Sorry, the regular vscode version 1.17.2 doing just fine. That's only happen on insider build

@mxschmitt
Copy link
Member

Tried to reproduce, but in my version everything is working fine. Already tried to reproduce it without extensions?

  • VSCode Version: Code - Insiders 1.18.0-insider (c1e079b, 2017-10-25T04:18:36.616Z)
  • OS Version: Windows_NT x64 6.1.7601

@vadim-su
Copy link

I have the same problem.
screenshot_20171025_144545

  • VSCode Version: 1.17.2
  • OS Version: Linux fort_dey 4.13.8-1-ARCH Open Source VS Code #1 SMP PREEMPT Wed Oct 18 11:49:44 CEST 2017 x86_64 GNU/Linux

Installed addons:
screenshot_20171025_145043

@vadim-su
Copy link

It seems to me that the problem is in the font.
I changed the fontFamily ("editor.fontFamily": "'Noto Mono', 'Droid Sans Mono', 'Courier New', monospace, 'Droid Sans Fallback'") and the character displayed correctly.
screenshot_20171025_145922

@tangorboyz
Copy link
Author

I don't know, it's working again. I even didn't have to disable the extensions.

@tangorboyz
Copy link
Author

tangorboyz commented Oct 25, 2017

You're right, it's the font. Thanks.

@jhasse
Copy link
Contributor

jhasse commented Oct 27, 2017

Still not fixed for me, even when using "editor.fontFamily": "'Noto Mono', 'Droid Sans Mono', 'Courier New', monospace, 'Droid Sans Fallback'" (with or without Noto Mono installed). I'm on Fedora 26 and using 1.17.2.

@Tyriar
Copy link
Member

Tyriar commented Oct 28, 2017

Duplicate #35901

@Tyriar Tyriar closed this as completed Oct 28, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Oct 28, 2017
@abhigyandwivedi
Copy link

@jhasse changing my font family in user settings file to "editor.fontFamily": "monospace,'Noto Mono', 'Droid Sans Mono', 'Courier New', 'Droid Sans Fallback'" resolved this issue completely.

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

6 participants