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

There is no merits in one-liner text terminal prompt - go full-blown text windows #3777

New Issue
Open
opened 2026-01-30 23:29:54 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 23:29:54 +00:00
Owner
Copy Link

Originally created by @sq2500 on GitHub (Sep 7, 2019).

Description of the new feature/enhancement

There is no merits in one-liner text terminal console - boldly use proper IDE text windows

  • With 2K, 4K display "estate" it make absolute no sense to stick with one-liner terminal prompts
  • enable multiple split-view windows like a text editor.

Enables better integration across traditional keystroke/shortcuts UI, GUI and mouse-clicks.
One-line prompt were invented in days with limited resources.

Today Console UI's does not need to follow in "exact" same foot steps - proper editor windows would supplement the Console UI more conveniently when it comes to features such as history, searches, line numbers, also ease script editing.

Multiple split-view windows would be kind of loading various (text) files from last or save session together a interactive script interpreter.

VS Code has most of the plumping, line-by-line debugging already.
Keyboard shortcuts easy accessible by and re-assignable.

Features like on-the-fly filenames highlighting (current folder, folders in the path), Output redirection, Output Error codes & Hyper Linking, Line numbers etc. could major productivity gain benefits over a more traditional one-liner console prompt interface.

Text-click selection expansion similar to Excel cell selection range expansion.
Browser like ALT+click to open/launch/clipboard/buffer copy for selected text.
MDI split screen views for file load, file save, history will make it easier for the console users.

Combination of both GUI keyboard shortcuts, traditional console keyboard shortcuts enable larger user base, also make it easier for newbies.

Traditional Console keyboard shortcuts should take precedence, also allow conflicting GUI keyboard shortcuts to reassigned or preferably used by keyboard modifier keys.

F. ex.:
WIN key ==> GUI
CTRL/ALT/SHIFT key ==> console

"Standard" keyboard shortcuts could be used in a larger context, also more quickly become "natural".
Configurable mouse-click interactions with the console prompt.

Enables Terminal console UI interaction with Windows GUI applications.

Proposed technical implementation details (optional)

Split screen buffer views: 0..9, Q-P (scrollable splitview windows)
Side by side buffer views for copy/paste/diff/highlighting

"Standard" window buffers available for copy/paste/search/replace/regexp (NFA)
Buffer 0: Clipboard Text
Buffer 1: Search, Replace output
Buffer 2: Filenames, symbol links, (folder view)
Buffer 3: Matched searches/replaced (like find all)
Buffer 4: Command History
Buffer 5: Filename History (recent filelist)
Buffer 6: Edit history (column-view of keystroke, filename, date/time like VS Code Ctrl+K+S)
Buffer 7: Diff history
Buffer 8: Regexp history
Buffer 9: Output history applications (stdout, stderr, date/time)

Re-assignable keyboard shortcuts.
Traditional keyboard shortcuts take precedence over conflicting GUI shortcuts.
Keyboard modifier keys, WIN+ for GUI, CTL+ALT+SHIFT combination for Terminal
Proper editing in Text window and also faster than "spinning" single text-line "up-down"

Proposed technical implementation details (optional)

Originally created by @sq2500 on GitHub (Sep 7, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 is no merits in one-liner text terminal console - boldly use proper IDE text windows - With 2K, 4K display "estate" it make absolute no sense to stick with one-liner terminal prompts - enable multiple split-view windows like a text editor. Enables better integration across traditional keystroke/shortcuts UI, GUI and mouse-clicks. One-line prompt were invented in days with limited resources. Today Console UI's does not need to follow in "exact" same foot steps - proper editor windows would supplement the Console UI more conveniently when it comes to features such as history, searches, line numbers, also ease script editing. Multiple split-view windows would be kind of loading various (text) files from last or save session together a interactive script interpreter. VS Code has most of the plumping, line-by-line debugging already. Keyboard shortcuts easy accessible by and re-assignable. Features like on-the-fly filenames highlighting (current folder, folders in the path), Output redirection, Output Error codes & Hyper Linking, Line numbers etc. could major productivity gain benefits over a more traditional one-liner console prompt interface. Text-click selection expansion similar to Excel cell selection range expansion. Browser like ALT+click to open/launch/clipboard/buffer copy for selected text. MDI split screen views for file load, file save, history will make it easier for the console users. Combination of both GUI keyboard shortcuts, traditional console keyboard shortcuts enable larger user base, also make it easier for newbies. Traditional Console keyboard shortcuts should take precedence, also allow conflicting GUI keyboard shortcuts to reassigned or preferably used by keyboard modifier keys. F. ex.: WIN key ==> GUI CTRL/ALT/SHIFT key ==> console "Standard" keyboard shortcuts could be used in a larger context, also more quickly become "natural". Configurable mouse-click interactions with the console prompt. <!-- 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). --> Enables Terminal console UI interaction with Windows GUI applications. # Proposed technical implementation details (optional) Split screen buffer views: 0..9, Q-P (scrollable splitview windows) Side by side buffer views for copy/paste/diff/highlighting "Standard" window buffers available for copy/paste/search/replace/regexp (NFA) Buffer 0: Clipboard Text Buffer 1: Search, Replace output Buffer 2: Filenames, symbol links, (folder view) Buffer 3: Matched searches/replaced (like find all) Buffer 4: Command History Buffer 5: Filename History (recent filelist) Buffer 6: Edit history (column-view of keystroke, filename, date/time like VS Code Ctrl+K+S) Buffer 7: Diff history Buffer 8: Regexp history Buffer 9: Output history applications (stdout, stderr, date/time) Re-assignable keyboard shortcuts. Traditional keyboard shortcuts take precedence over conflicting GUI shortcuts. Keyboard modifier keys, WIN+ for GUI, CTL+ALT+SHIFT combination for Terminal Proper editing in Text window and also faster than "spinning" single text-line "up-down" <!-- 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). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-30 23:29:54 +00:00
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 Resolution-Duplicate
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#3777
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?