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.

Sign up for GitHub

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

Jump to bottom

VS Code Terminal Kerning Way Off after latest update - 1.17.1 #36172

Closed
alohaninja opened this issue Oct 12, 2017 · 3 comments
Closed

VS Code Terminal Kerning Way Off after latest update - 1.17.1 #36172

alohaninja opened this issue Oct 12, 2017 · 3 comments
Assignees
@Tyriar
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@alohaninja
Copy link

Can you please fix the kerning in the terminal - it's so far off! It's driving me nuts. The font in the editor should be the same as the font in the terminal. It's killing me...

terminal vscode2

  • VSCode Version: Code 1.17.1 (1e9d365, 2017-10-10T14:24:41.632Z)
  • OS Version: Windows_NT ia32 10.0.15063
  • Extensions:
Extension Author (truncated) Version
npm-intellisense chr 1.3.0
gitlens eam 5.6.3
tslint eg2 1.0.11
beautify Hoo 1.1.1
docthis joe 0.5.0
prettify-json moh 0.0.3
mssql ms- 1.2.0
PowerShell ms- 1.4.3
material-icon-theme PKi 2.2.2
vscode-icons rob 7.15.0
vscode-hexdump sle 1.4.0
vscode-jumpy wma 0.3.1

Steps to Reproduce:

Reproduces without extensions: Yes/No
image
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Oct 12, 2017
@alohaninja
Copy link
Author

Looks like the editor has a setting "editor.letterSpacing" but that doesn't exist for integrated terminal...

"terminal.integrated.letterSpacing" should be added or fix the spacing between the letters to match the editor.

@alohaninja alohaninja mentioned this issue Oct 12, 2017
Closed
@alohaninja
Copy link
Author

alohaninja commented Oct 12, 2017 •
edited
Loading

this does seem to be rendering correctly using VS Code insiders...thanks for the quick fix!

I was looking for a way to downgrade, but updating to the preview release will work also!

@Tyriar
Copy link
Member

Tyriar commented Oct 28, 2017

Sorry about the hassle, this one was tracked in #35991

@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
@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.
Assignees

@Tyriar Tyriar

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
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Tyriar @chrmarti @alohaninja and others