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

Add command history based on current folder #17782

New Issue
Closed
opened 2026-01-31 05:53:18 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 05:53:18 +00:00
Owner
Copy Link

Originally created by @Liero on GitHub (Jun 23, 2022).

Currently, when I press Up/Down arrow keys, the Terminal suggest previously entered commands.

I want to traverse only previously entered commands in current folder.

Example:

After following sequence of commands:

C:\repo> git commit
C:\repo> cd src\app
C:\repo\src\app> git rm file1.txt
C:\repo\src\app> cd ..\..
C:\repo>

a new keyboard shorcut like PageUp or Ctrl+Up would suggest cd src\app and then git commit, because they were the last commands executed in the directory.

Originally created by @Liero on GitHub (Jun 23, 2022). Currently, when I press Up/Down arrow keys, the Terminal suggest previously entered commands. I want to traverse only previously entered commands in current folder. Example: After following sequence of commands: ``` C:\repo> git commit C:\repo> cd src\app C:\repo\src\app> git rm file1.txt C:\repo\src\app> cd ..\.. C:\repo> ``` a new keyboard shorcut like `PageUp` or `Ctrl+Up` would suggest `cd src\app` and then `git commit`, because they were the last commands executed in the directory.
claunia added the Issue-FeatureIssue-QuestionNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 05:53:18 +00:00
claunia commented 2026-01-31 05:53:19 +00:00
Author
Owner
Copy Link

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

This is a really interesting idea - probably not one that's immediately viable, but an interesting idea nonetheless.

I started typing up a response here and realized I just had a lot of thoughts here, probably more than I had time to type. So my apologies for the kinda random collection of thoughts here

The history is actually provided by the shell, not the Terminal[1]. This would be a really good request for PowerShell / PSReadline, since that's actively maintained and has all sorts of fancy completions. The intelligent auto-complete that they shipped recently might actually just do this. I'm not as familiar with pwsh as I should be.

This does have interesting ties though to #1595, #12863. cd src/app is maybe a bit trivial compared to what I expected for that, but it still counts. Is there a good way for us to stash that relative to the CWD, so that it's a quickly accessible command? Probably not as easy as just up.

[1]: technically, cmd.exe's history actually is powered by conhost. But conhost has no idea what the CWD of a process is. I suppose it could theoretically be told what the CWD is, in the same way the Terminal is, and if it is told the CWD, stash history as a map of dir -> [history]. But there's no good way to pass settings to conhost for something like that.

We theoretically wouldn't really need to worry about back-compat on this one, cause you've already opt'd in to telling us the CWD, no legacy app is gonna accidentally set that.

@zadjii-msft commented on GitHub (Jun 23, 2022): This is a really interesting idea - probably not one that's immediately viable, but an interesting idea nonetheless. _I started typing up a response here and realized I just had a lot of thoughts here, probably more than I had time to type. So my apologies for the kinda random collection of thoughts here_ The history is actually provided by the shell, not the Terminal[1]. This would be a really good request for PowerShell / PSReadline, since that's actively maintained and has all sorts of fancy completions. The intelligent auto-complete that they shipped recently might actually just do this. I'm not as familiar with pwsh as I should be. This does have interesting ties though to #1595, #12863. `cd src/app` is maybe a bit trivial compared to what I expected for that, but it still counts. Is there a good way for us to stash that relative to the CWD, so that it's a quickly accessible command? Probably not as easy as just <kbd>up</kbd>. [1]: _technically_, `cmd.exe`'s history actually is powered by conhost. But conhost has no idea what the CWD of a process is. I suppose it could theoretically be told what the CWD is, in the same way the Terminal is, and if it is told the CWD, stash history as a map of `dir -> [history]`. But there's no good way to pass settings to conhost for something like that. We theoretically wouldn't really need to worry about back-compat on this one, cause you've already opt'd in to telling us the CWD, no legacy app is gonna _accidentally_ set that.
claunia commented 2026-01-31 05:53:20 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Mar 20, 2023):

Hi @Liero. As Mike said, (with the exception of CMD) shells are the ones responsible for the command history, not the Terminal. We discussed this feature more as a team today, and adding that kind of responsibility to Terminal further complicates the relationship between Terminal and the attached shell, which could be a problem for new users, especially if they switch between different terminal emulators. This might be a better suggestion for "Clink" or "Yori".

@carlos-zamora commented on GitHub (Mar 20, 2023): Hi @Liero. As Mike said, (with the exception of CMD) shells are the ones responsible for the command history, not the Terminal. We discussed this feature more as a team today, and adding that kind of responsibility to Terminal further complicates the relationship between Terminal and the attached shell, which could be a problem for new users, especially if they switch between different terminal emulators. This might be a better suggestion for "Clink" or "Yori".
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 Issue-Question 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#17782
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?