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

Where is the straight forward, direct link to all the keyboard shortcuts of this extension? #3

Open
rebornix opened this issue Feb 27, 2018 · 3 comments

Comments

@rebornix
Copy link
Member

From @fmorriso on December 17, 2017 14:23

"You can see all the keyboard shortcuts in the extension's contribution list."

What does this mean? I cannot find it.

Please provide a straight-forward, easy-to-find, direct link on the main page of this extension to a list (such as markdown or pdf) of the replacement keyboard shortcuts this extension supplies.

Copied from original issue: rebornix/vscode-vs-keybindings#26

@rebornix
Copy link
Member Author

From @cpmcgrath on February 5, 2018 0:15

If you go to the Extension list in Visual Studio Code, find Visual Studio Keymap (Doesn't need to be installed), it brings up details of the Extension. Up the top, it shows 4 sections: Details, Contributions, Changelog, Dependencies. If you choose Contributions it shows all the commands and what they map to.

@rebornix
Copy link
Member Author

From @fmorriso on February 5, 2018 11:39

Looking in Contributions instead of something like Documentation or Keyboard Shortcuts is not straight forward. You cannot play this type of peek-a-boo with the documentation of how to use an extension and expect wide-spread adoption.

@rebornix
Copy link
Member Author

From @cpmcgrath on February 5, 2018 20:12

I agree that it's more hidden than ideal, however, that's the standard documentation location for this in Visual Studio Code.
With that in mind, I think if you believe it's too hidden I'd suggest raising it with the Visual Studio Code team.

By using it as the shortcut documentation, it means the extension only has to maintain a single list of changes instead of two. I agree with the Author's decision to use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant