starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Feature Request: Reverse Command Output Orientation in Windows Terminal #21988

New Issue
Closed
opened 2026-01-31 08:00:10 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 08:00:10 +00:00
Owner
Copy Link

Originally created by @Alemar16 on GitHub (Jul 20, 2024).

Description of the new feature/enhancement

Currently, the Windows Terminal and PowerShell prompt are aligned at the top, and the output of commands descends as more commands are entered. This is the standard behavior, but I am looking for an option to reverse this behavior.

I would like an option in the Windows Terminal settings that allows the prompt to be aligned at the bottom of the terminal window, and for the command outputs to ascend upwards. This would mean that the most recent command and its output are at the bottom, and previous commands and outputs move upwards as new commands are entered. This behavior is similar to the terminal Warp.

This feature would be particularly useful for users who prefer having the most recent command at the bottom of their screen, similar to chat applications or other interfaces where new content appears at the bottom.

Proposed technical implementation details (optional)

Add a configuration option in the settings.json file that allows users to choose the orientation of the prompt and command outputs. This setting would enable users to switch between the traditional top-down orientation and the requested bottom-up orientation.

Originally created by @Alemar16 on GitHub (Jul 20, 2024). # Description of the new feature/enhancement Currently, the Windows Terminal and PowerShell prompt are aligned at the top, and the output of commands descends as more commands are entered. This is the standard behavior, but I am looking for an option to reverse this behavior. I would like an option in the Windows Terminal settings that allows the prompt to be aligned at the bottom of the terminal window, and for the command outputs to ascend upwards. This would mean that the most recent command and its output are at the bottom, and previous commands and outputs move upwards as new commands are entered. This behavior is similar to the terminal Warp. This feature would be particularly useful for users who prefer having the most recent command at the bottom of their screen, similar to chat applications or other interfaces where new content appears at the bottom. # Proposed technical implementation details (optional) Add a configuration option in the settings.json file that allows users to choose the orientation of the prompt and command outputs. This setting would enable users to switch between the traditional top-down orientation and the requested bottom-up orientation.
claunia commented 2026-01-31 08:00:11 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jul 21, 2024):

This sounds very much like issue #14773. Is that the kind of thing you're looking for?

@j4james commented on GitHub (Jul 21, 2024): This sounds very much like issue #14773. Is that the kind of thing you're looking for?
claunia commented 2026-01-31 08:00:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 22, 2024):

Yea, I think this would have to be #14773, rather than something like:

image

@zadjii-msft commented on GitHub (Jul 22, 2024): Yea, I think this would have to be #14773, rather than something like: ![image](https://github.com/user-attachments/assets/423a7077-63b3-4357-8ded-22c919500792)
claunia commented 2026-01-31 08:00:12 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 26, 2024):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Jul 26, 2024): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Feature Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21988
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?