VSC-like recent used command in command plate (search result) #17021

Closed
opened 2026-01-31 05:30:03 +00:00 by claunia · 2 comments
Owner

Originally created by @Civon on GitHub (Mar 16, 2022).

Description of the new feature/enhancement

A VSCode-like recently used (history) command in the command plate is very helpful by doing repeated jobs.
Scenarios:

  1. executing a command that does not have a shortcut, like "rename tab title" or "toggle always on top mode". With this feature on, you can save time to type at least two keywords to do so. You can switch tab than re-do it with "ctrl + shift + p" + enter.

  2. skip unwanted alike command. You want to new a tab that you can not tell it is profile 7 or 8. Without a mouse, you will be willing to use the nested command "new tab... with >", but, as image, you may need too press tons of down arrow to reach that command instead of the one without nested command.
    image
    Maybe you will later find out: you can do this by ⌨"ctrl + shift + space" or adding "..." in search.
    But, I think the command plate's purpose is to ease the pain/gives hint before you learnt the shortcut.

Proposed technical implementation details (optional)

Originally created by @Civon on GitHub (Mar 16, 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 A VSCode-like recently used (history) command in the command plate is very helpful by doing repeated jobs. Scenarios: 1. executing a command that does not have a shortcut, like "rename tab title" or "toggle always on top mode". With this feature on, you can save time to type at least two keywords to do so. You can switch tab than re-do it with "ctrl + shift + p" + enter. 2. skip unwanted alike command. You want to new a tab that you can not tell it is profile 7 or 8. Without a mouse, you will be willing to use the nested command "new tab... with >", but, as image, you may need too press tons of down arrow to reach that command instead of the one without nested command. ![image](https://user-images.githubusercontent.com/24861096/158698693-808c8fa6-8e5c-4267-899d-0c2e6e08ccd5.png) Maybe you will later find out: you can do this by ⌨"ctrl + shift + space" or adding "..." in search. But, I think the command plate's purpose is to ease the pain/gives hint before you learnt the shortcut. <!-- 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-31 05:30:03 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Mar 17, 2022):

In general, I think you're looking for the same thing as #6647.

FWIW, the command palette does do "fuzzy" matching, so typing nt. will probably automatically filter to New Tab... for you.

Thanks!

/dup #6647

@zadjii-msft commented on GitHub (Mar 17, 2022): In general, I think you're looking for the same thing as #6647. FWIW, the command palette does do "fuzzy" matching, so typing `nt.` will probably automatically filter to `New Tab...` for you. Thanks! /dup #6647
Author
Owner

@ghost commented on GitHub (Mar 17, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 17, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17021