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

Resizing Terminal window is slow and laggy #5905

Closed
ghost opened this issue May 14, 2020 · 2 comments
Closed

Resizing Terminal window is slow and laggy #5905

ghost opened this issue May 14, 2020 · 2 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@ghost
Copy link

ghost commented May 14, 2020

Steps to reproduce

Resizing the Terminal window is slow and laggy. It feels like I'm resizing the window of a uwp app, instead of a Terminal app. Terminals can't be slow and terminals can't have graphical lags.

Expected behavior

Resizing the window should be as smooth as resizing a windows console window.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels May 14, 2020
@zadjii-msft
Copy link
Member

@phgmacedo Cloud you try disabling a setting for me, to see if that helps here? Could you add "snapToGridOnResize": false to your settings.json file? That setting forces the terminal to try and snap to the nearest character size - if you disable it, the Terminal will resize more smoothly.

I'm not saying that resizing isn't slow, it's one of the worst functions in the codebase. Heck, optimizing it is what #5800 is all about. But the above setting might make it feel smoother, at least for now.

@zadjii-msft zadjii-msft added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 14, 2020
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label May 18, 2020
@ghost
Copy link

ghost commented May 18, 2020

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost ghost closed this as completed May 21, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zadjii-msft