Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to access commands without typing #54348

Closed
sirgru opened this issue Jul 15, 2018 · 2 comments
Closed

Add ability to access commands without typing #54348

sirgru opened this issue Jul 15, 2018 · 2 comments
Assignees
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code ux User experience issues
Milestone

Comments

@sirgru
Copy link

sirgru commented Jul 15, 2018

AFAIK the only way to access commands from different extensions is through the use of command palette. This works like a big bag of commands that we filter to the commands we want.

It would be better to be able to access the commands through some other more structured way, instead of having to type them every time or use history. Having to remember the wording for the concepts extension developers made is a pain point. Also, the commands are not discoverable in this way. Currently the team has refused to add a basic toolbar, which I consider a common sense feature. #41309 To achieve this basic functionality people put commands in the status bar, which is a hacky inconvenient way. https://marketplace.visualstudio.com/items?itemName=fabiospampinato.vscode-commands

Irrespective of the toolbar feature, I propose another menu "Commands" where commands from different extensions are automatically added and grouped by extension name. This would aid in discoverability and also users wouldn't have to waste time typing command names.

@jrieken jrieken removed their assignment Jul 16, 2018
@Tyriar Tyriar added the feature-request Request for new features or functionality label Jul 16, 2018
@chrisdias chrisdias added the ux User experience issues label Sep 21, 2018
@chrisdias chrisdias assigned miguelsolorio and unassigned chrisdias Dec 11, 2020
@moon6969
Copy link

Could you please add "Accessibility" label to this issue? It's difficult for me to use the keyboard all the time.

@chrisdias chrisdias added the accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues label Dec 16, 2020
@miguelsolorio miguelsolorio added this to the Backlog milestone Oct 4, 2021
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Nov 1, 2022
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code ux User experience issues
Projects
None yet
Development

No branches or pull requests

9 participants