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

Closed
opened 2026-01-31 05:48:22 +00:00 by claunia · 2 comments
Owner

Originally created by @tomviolin on GitHub (Jun 5, 2022).

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.

Originally created by @tomviolin on GitHub (Jun 5, 2022). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # 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. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> 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) <!-- A clear and concise description of what you want to happen. --> 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.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 05:48:22 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jun 6, 2022):

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 commented on GitHub (Jun 6, 2022): 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
Author
Owner

@ghost commented on GitHub (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 commented on GitHub (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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17633