Command History (F7) is added to when selected command from the list #22156

Open
opened 2026-01-31 08:04:57 +00:00 by claunia · 2 comments
Owner

Originally created by @MogHughson on GitHub (Aug 24, 2024).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

1.20.11781.0

Windows build number

10.0.22631.4037

Other Software

No response

Steps to reproduce

  1. Open a clean command prompt - nothing in the list in F7.
  2. Type in a command, e.g. "dir"
  3. Type in a second different command, e.g. "dir D*"
  4. Press F7 to see the command list - it will contain two commands. Select the first one from the list.
  5. Press F7 to see the command list again, it will now contain three commands. This is unexpected.

Expected Behavior

Selecting the command from the command list was previously (in Windows 10 command prompt) the way you issued it to ensure it didn't get added to the history, thus allowing you to maintain a nice tidy command list.

Actual Behavior

Instead it was added to the history.

Originally created by @MogHughson on GitHub (Aug 24, 2024). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version 1.20.11781.0 ### Windows build number 10.0.22631.4037 ### Other Software _No response_ ### Steps to reproduce 1. Open a clean command prompt - nothing in the list in F7. 2. Type in a command, e.g. "dir" 3. Type in a second different command, e.g. "dir D*" 4. Press F7 to see the command list - it will contain two commands. Select the first one from the list. 5. Press F7 to see the command list again, it will now contain three commands. This is unexpected. ### Expected Behavior Selecting the command from the command list was previously (in Windows 10 command prompt) the way you issued it to ensure it didn't get added to the history, thus allowing you to maintain a nice tidy command list. ### Actual Behavior Instead it was added to the history.
claunia added the Product-ConhostIssue-BugArea-CookedRead labels 2026-01-31 08:04:57 +00:00
Author
Owner

@lhecker commented on GitHub (Nov 21, 2024):

As per #18138 I've decided to revert this change for now.

@lhecker commented on GitHub (Nov 21, 2024): As per #18138 I've decided to revert this change for now.
Author
Owner

@carlos-zamora commented on GitHub (Nov 25, 2024):

Discussed a bit as a team. Some notes:

  • Need to look at this case a little more. Intersection of command history popup and error navigation.
  • from #17797:
    • " Expected Behavior: Selecting the command from the command list was previously (in Windows 10 command prompt) the way you issued it to ensure it didn't get added to the history, thus allowing you to maintain a nice tidy command list."
    • suggests it's not about the deduplication itself, more just that the workflow is a little different.
@carlos-zamora commented on GitHub (Nov 25, 2024): Discussed a bit as a team. Some notes: - Need to look at this case a little more. Intersection of command history popup and error navigation. - from #17797: - " Expected Behavior: Selecting the command from the command list was previously (in Windows 10 command prompt) the way you issued it to ensure it didn't get added to the history, thus allowing you to maintain a nice tidy command list." - suggests it's not about the deduplication itself, more just that the workflow is a little different.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#22156