-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Text in middle of terminal section blurred since upgrade to 1.45.0 #97682
Comments
Please provide a screenshot of a gif illustrating the problem. See this wiki page for more general info on how to report actionable terminal issues. /label "needs more info" integrated-terminal |
Hope PNG is ok - have attached 2 screenshots, one of which show fuzzy
text in the terminal window (half way along top of terminal is
worst). Minimising and restoring doesn't fix it; switching from full
screen to reduced size and back does.
…On Thu, 2020-06-11 at 05:32 -0700, Daniel Imms wrote:
Please provide a screenshot of a gif illustrating the problem. See
this wiki page for more general info on how to report actionable
terminal issues.
/label "needs more info" integrated-terminal
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "
#97682 (comment)
",
"url": "
#97682 (comment)
",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
@wivory attaching via email doesn't work on github, you need to go to github.com for that. |
OK – will need to wait until I’m back at work on Monday then.
Thanks,
William
From: Daniel Imms <notifications@github.com>
Sent: 13 June 2020 16:48
To: microsoft/vscode <vscode@noreply.github.com>
Cc: wivory <wjivory@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [microsoft/vscode] Text in middle of terminal section blurred since upgrade to 1.45.0 (#97682)
@wivory <https://github.com/wivory> attaching via email doesn't work on github, you need to go to github.com for that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#97682 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEUR242P5BDVHGDC3SG3XK3RWONTRANCNFSM4M7PSGZQ> . <https://github.com/notifications/beacon/AEUR24ZTDFJODZMBMB4L2G3RWONTRA5CNFSM4M7PSGZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZOS5II.gif>
|
``<script src="//code.jivosite.com/widget/p3yqJKpweV" async></script> |
[<script src="//code.jivosite.com/widget/p3yqJKpweV" async></script>](<script src="//code.jivosite.com/widget/p3yqJKpweV" async></script>b19cEXMX1mxH3) #98778 |
Can you share your settings.json? Try changing your |
{
"python.testing.nosetestsEnabled": true,
"editor.formatOnSave":
true,
"editor.acceptSuggestionOnEnter": "off",
"editor.rulers":
[
80,
120
],
"go.buildOnSave": "off",
"go.vetOnS
ave": "off",
"go.formatTool": "gofmt",
"workbench.colorTheme": "D
efault Light+",
"files.trimTrailingWhitespace": true,
"editor.ren
derWhitespace": "boundary",
"[groovy]": {},
"python.testing.pytes
tEnabled": true,
"editor.multiCursorModifier": "ctrlCmd",
"worksp
aceExplorer.workspaceStorageDirectory": "/home/wivory/VSCodeWorkspaces"
,
"groovyLint.basic.run": "onType",
"jenkins.pipeline.linter.conn
ector.url": "http://scottykins.edi.vyatta.net/pipeline-model-
converter/validate",
"jenkins.pipeline.linter.connector.user": "admi
n",
"jenkins.pipeline.linter.connector.pass": "admin",
"[c]": {
"editor.formatOnSave": false
},
"files.exclude": {
"**/build": true
},
"[robot]": {
"editor.tabSize":
4
},
"window.zoomLevel": -1,
"C_Cpp.default.defines": []
}
…On Mon, 2020-06-15 at 06:50 -0700, Daniel Imms wrote:
Can you share your settings.json?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "
#97682 (comment)
",
"url": "
#97682 (comment)
",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Workaround is to use the setting |
Thanks - that appears to have fixed the problem.
Regards,
William
…On Wed, 2020-07-08 at 14:33 -0700, Daniel Imms wrote:
Workaround is to use the setting "terminal.integrated.rendererType":
"dom"
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "
#97682 (comment)
",
"url": "
#97682 (comment)
",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
@wivory yes that looks like a different thing, probably related to Electron so you could search the issues for electron/blurry. Another potential workaround is to make sure |
Upgraded to 1.56 today. Problem is back as it seems the rendererType option is now greyed out in settings.json and doesn't work. Coming up to a year after I first filed this )-: |
@wivory it changed to: |
Let's track this in #85154 /duplicate |
Issue Type: Bug
Steps to Reproduce:
This only started on Monday this week after I upgraded to 1.45.0.
VS Code version: Code 1.45.0 (d69a79b, 2020-05-07T16:10:24.511Z)
OS version: Linux x64 4.15.0-99-generic
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: disabled_off_ok
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Extensions (16)
The text was updated successfully, but these errors were encountered: