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

Delete command from the history? #17509

New Issue
Closed
opened 2026-01-31 05:44:37 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:44:37 +00:00
Owner
Copy Link

Originally created by @Suncatcher on GitHub (May 18, 2022).

Description of the new feature/enhancement

Sometime we need to clean out unnecessary commands from the history, but keep all the rest, so it shouldn't be a total history wipe.

Proposed technical implementation details (optional)

In *nix we have a very nice and nifty command that does exactly that:

history -d linenumber

We should have the same capability in Windows Terminal as well.

Originally created by @Suncatcher on GitHub (May 18, 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 Sometime we need to clean out unnecessary commands from the history, but keep all the rest, so it shouldn't be a total history wipe. <!-- 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. --> In *nix we have a very nice and nifty command that does exactly that: history -d linenumber We should have the same capability in Windows Terminal as well.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:44:37 +00:00
claunia commented 2026-01-31 05:44:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 18, 2022):

Commandline history is something that is largely driven on a per-shell basis. Which shell are you using? cmd? powershell/?

I bet that PowerShell already has a similar feature. cmd probably not as much, though there is GetConsoleHistoryInfo/SetConsoleHistoryInfo, which I'm sure doskey can modify in a more user friendly way.

@zadjii-msft commented on GitHub (May 18, 2022): Commandline history is something that is largely driven on a per-shell basis. Which shell are you using? `cmd`? `powershell`/? I bet that PowerShell already has a similar feature. `cmd` probably not as much, though there is `GetConsoleHistoryInfo`/`SetConsoleHistoryInfo`, which I'm sure `doskey` can modify in a more user friendly way.
claunia commented 2026-01-31 05:44:39 +00:00
Author
Owner
Copy Link

@Suncatcher commented on GitHub (May 18, 2022):

Which shell are you using? cmd? powershell?

PS 7.2.3.

I believe cmd has no history capability, so it is pretty irrelevant for this feature request. Unless of course Windows Terminal adds own history on top of cmd

@Suncatcher commented on GitHub (May 18, 2022): > Which shell are you using? cmd? powershell? PS 7.2.3. I believe `cmd` has no history capability, so it is pretty irrelevant for this feature request. Unless of course Windows Terminal adds own history on top of `cmd`
claunia commented 2026-01-31 05:44:39 +00:00
Author
Owner
Copy Link

@Suncatcher commented on GitHub (May 18, 2022):

I bet that PowerShell already has a similar feature

Yes it already has. It is Clear-History -ID 12, 20 cmdlet. But I observe it behaves weird on the Terminal. Example:

image

I use Get-History cmdlet to get the commands IDs. but it fetches me the history only of current terminal session, however by arrow keys I can access all commands from the past. How to access all IDs?

@Suncatcher commented on GitHub (May 18, 2022): > I bet that PowerShell already has a similar feature Yes it already has. It is `Clear-History -ID 12, 20` cmdlet. But I observe it behaves weird on the Terminal. Example: ![image](https://user-images.githubusercontent.com/6388034/169035300-ee60bccd-bc8d-4f08-9c90-c0dd2bbdc6d9.png) I use Get-History cmdlet to get the commands IDs. but it fetches me the history only of **current terminal session**, however by arrow keys I can access all commands from the past. How to access all IDs?
claunia commented 2026-01-31 05:44:39 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (May 18, 2022):

For current command history list:

help Clear-History

And you can empty or delete $env:AppData\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt

@237dmitry commented on GitHub (May 18, 2022): For current command history list: ``` help Clear-History ``` And you can empty or delete `$env:AppData\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt`
claunia commented 2026-01-31 05:44:40 +00:00
Author
Owner
Copy Link

@Suncatcher commented on GitHub (May 18, 2022):

And you can empty or delete $env:AppData\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt

thanks, that worked. I'm closing this ticket, but hotkey for this would be much more convenient than editing this file.

@Suncatcher commented on GitHub (May 18, 2022): > And you can empty or delete $env:AppData\Microsoft\Windows\PowerShell\PSReadLine\ConsoleHost_history.txt thanks, that worked. I'm closing this ticket, but hotkey for this would be much more convenient than editing this file.
claunia commented 2026-01-31 05:44:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 18, 2022):

hotkey for this would be much more convenient than editing this file

Agreed! That is a request you should file on https://github.com/PowerShell/PSReadLine, though, as they control the storage and manipulation of history in PowerShell.

@DHowett commented on GitHub (May 18, 2022): > hotkey for this would be much more convenient than editing this file Agreed! That is a request you should file on https://github.com/PowerShell/PSReadLine, though, as they control the storage and manipulation of history in PowerShell.
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-Attention Needs-Tag-Fix Needs-Triage
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#17509
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?