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

VIM based controls for whole windows #37160

Closed
vishnuvizz opened this issue Jan 30, 2025 · 1 comment
Closed

VIM based controls for whole windows #37160

vishnuvizz opened this issue Jan 30, 2025 · 1 comment
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Resolution-Already Fixed/Doesn't Apply A change in the product has made the issue obsolete.

Comments

@vishnuvizz
Copy link

Description of the new feature / enhancement

Navigating within Windows is a fundamental task in any workflow. To enhance efficiency, users often rely on keyboard shortcuts. However, the lack of standardization and application-specific shortcuts makes it difficult to memorize and adapt to them.

My main request is to implement system-wide navigation shortcuts based on VIM-style keybindings. This would provide a consistent experience across applications, reducing the need to relearn different shortcuts.

Scenario when this would be used?

Windows navigation

Supporting information

There exists several external tools for application specific keybindings, but it would be great to have system wide VIM keybindings.
https://github.com/erikw/vim-keybindings-everywhere-the-ultimate-list

@vishnuvizz vishnuvizz added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Jan 30, 2025
@Aaron-Junker
Copy link
Collaborator

You can remap your own shortcuts with Keyboard Manager. Making a os-wide vim mode, that would also work with all kinds of apps would be an incredible amount of effort, if it even was possible, this would be out-of scope for this project.

@Aaron-Junker Aaron-Junker closed this as not planned Won't fix, can't repro, duplicate, stale Jan 30, 2025
@Aaron-Junker Aaron-Junker added the Resolution-Already Fixed/Doesn't Apply A change in the product has made the issue obsolete. label Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Resolution-Already Fixed/Doesn't Apply A change in the product has made the issue obsolete.
Projects
None yet
Development

No branches or pull requests

2 participants