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

Recent commands UI #19307

New Issue
Closed
opened 2026-01-31 06:39:36 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 06:39:36 +00:00
Owner
Copy Link

Originally created by @KyodaiKen on GitHub (Feb 3, 2023).

Description of the new feature/enhancement

In Linux, almost every terminal stores a persistent history of commands. I think in this case it's the interpreter like bash or zsh. But I think it should be possible to do it on app level per user as well.

Proposed technical implementation details (optional)

A simple SQLite DB file per user and per command interpreter (cmd, powershell, etc.) that stores the history of commands could be used. The location should be configurable in the preferences JSON.

  1. User enters:

    backup f: n:\backups\computername\system
format f:

  2. User closes terminal and maybe even reboots windows

  3. User opens terminal back up and can push the arrow up key to recall the last commands they have executed.

  4. User cannot find what they're searching for, so they type:

    history

    And sees a list like this:

    0 2022-02-03 14:33: backup f: n:\backups\computername\system
1 2022-02-03 14:43: format f:

    And can redo the command using !1 or !0.
    With #0 the line pops up to be edited before executing with the RETURN key

Originally created by @KyodaiKen on GitHub (Feb 3, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 In Linux, almost every terminal stores a persistent history of commands. I think in this case it's the interpreter like `bash` or `zsh`. But I think it should be possible to do it on app level per user as well. <!-- 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 simple SQLite DB file per user and per command interpreter (cmd, powershell, etc.) that stores the history of commands could be used. The location should be configurable in the preferences JSON. <!-- A clear and concise description of what you want to happen. --> 1. User enters: ``` backup f: n:\backups\computername\system format f: ``` 2. User closes terminal and maybe even reboots windows 3. User opens terminal back up and can push the arrow up key to recall the last commands they have executed. 4. User cannot find what they're searching for, so they type: ``` history ``` And sees a list like this: ``` 0 2022-02-03 14:33: backup f: n:\backups\computername\system 1 2022-02-03 14:43: format f: ``` And can redo the command using `!1` or `!0`. With `#0` the line pops up to be edited before executing with the `RETURN` key
claunia added the Area-SettingsIssue-TaskIn-PRNeeds-Tag-FixProduct-Terminal labels 2026-01-31 06:39:36 +00:00
claunia commented 2026-01-31 06:39:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 3, 2023):

Sorry, this is just something that's got to be a feature of the shell (cmd.exe, pwsh, bash, etc) itself. PowerShell has supported this for some time via PsReadline, as do most other moder shells. Alas, cmd.exe will never be able to be changed to add this feature.

Now I had an idea in mind that might help mitigate this. It'd be a little wonky, but it would persist your command history regardless of shell. And since I don't really have a thread I'm already using for tracking that, I'm tempted to hijack this thread for that purpose.

My solution wouldn't be a CLI feature - it'd be build directly into the Terminal, and the history would be exposed via a UI element in the Terminal. You okay with me re-purposing this thread?

x-link #13445

@zadjii-msft commented on GitHub (Feb 3, 2023): Sorry, this is just something that's got to be a feature of the shell (`cmd.exe`, `pwsh`, `bash`, etc) itself. PowerShell has supported this for some time via PsReadline, as do most other moder shells. Alas, [`cmd.exe` will never be able to be changed](https://github.com/microsoft/terminal/blob/main/doc/Niksa.md#why-do-we-avoid-changing-cmdexe) to add this feature. Now I had an idea in mind that might help mitigate this. It'd be a little wonky, but it would persist your command history regardless of shell. And since I don't _really_ have a thread I'm already using for tracking that, I'm tempted to hijack this thread for that purpose. My solution wouldn't be a CLI feature - it'd be build directly into the Terminal, and the history would be exposed via a UI element in the Terminal. You okay with me re-purposing this thread? x-link #13445
claunia commented 2026-01-31 06:39:38 +00:00
Author
Owner
Copy Link

@KyodaiKen commented on GitHub (Feb 3, 2023):

That sounds nice! I actually proposed to add it to the Terminal app itself, I wouldn't have posted it here. You can of course hijack this thread. Let's see how it goes!

@KyodaiKen commented on GitHub (Feb 3, 2023): That sounds nice! I actually proposed to add it to the Terminal app itself, I wouldn't have posted it here. You can of course hijack this thread. Let's see how it goes!
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 Area-Settings In-PR Issue-Task Needs-Tag-Fix Product-Terminal
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#19307
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?