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

Terminal window usually opens with last few lines offscreen, requiring dragging window up #13228

Closed
tomviolin opened this issue Jun 5, 2022 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@tomviolin
Copy link

Description of the new feature/enhancement

There needs to be an option (or possibly default behavior) in which a new Terminal window's position automatically adjusts so that the entire Terminal character display is onscreen.

When the Terminal window opens with the last few lines offscreen, after a few commands the current prompt is not visible, requiring the user to stop typing, grab the mouse, and drag the window up. Worst case, the vertical size of the Terminal character display area exceeds the height of the screen, thus requiring both a resize downward of the window size using the top edge followed by dragging a part of the top tab area up to reveal the last few lines of the Terminal display. People who use Terminal are likely to be mostly typing commands and code, and it is very disruptive to have to stop typing and resize and move the Terminal window, every. single. time. a. new. terminal. window. is. opened.

Proposed technical implementation details (optional)

Append an adjustment calculation to the end of the current routine that calculates the position of a new Terminal window to move it and/or resize it such that the entire character display is visible on-screen and above any non-autohiding taskbar.

This could be an option, in case there are users who like the way it works now. But there probably aren't many.

@tomviolin tomviolin added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 5, 2022
@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 Jun 5, 2022
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11781 for more discussion.

/dup #11781

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2022
@ghost
Copy link

ghost commented Jun 6, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jun 6, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed 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 Jun 6, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants