-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
SCM Viewlet should be more keyboard friendly #90893
Comments
The contextual actions in each row can also be focused by pressing Tab and then Enter to execute. The only thing that I see missing is the fact that the SCM view loses focus once that happens. I can push a fix for that. Another thing I've decided to push is a Ctrl Shift Enter keybinding for lists which toggles the currently focused item from the selection. You could already kind of doing this with Shift Up/Down, but that would work only for consecutive elements. With Ctrl Enter, you can now select each item to be staged and then execute the action only once. |
Thanks for pushing a fix for this. Just tried to verify it but the insiders from 5 mins ago does not contain the fix. Will try it tomorrow. |
A problem I found is that using orca there is no return indicating that the file is selected or not when I press ctrl + shift + enter. |
Another problem using orca is that when I browse the list, orca does not announce the selected items, if one is selected. |
@jvesouza that sounds like an Orca issue. Can you maybe send a mail to the orca list and ask them the following:
|
@isidorn I'll check, thanks.
On my machine the orca is muted and I need to press tab and shift + tab to get the orca to respond normally. |
If instead of pressing the escape key I press the enter key to accept
the chosen operation, the problem also happens.
…On 2/20/20 10:35 AM, Isidor Nikolic wrote:
@jvesouza <https://github.com/jvesouza> thanks, I can reproduce that.
For that I filled a new issue #91085
<#91085>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90893?email_source=notifications&email_token=AAPRNESXNTYCCEFME77RH4LRD2BJFA5CNFSM4KXGL4EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMN5AZY#issuecomment-589025383>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPRNEX4F6RGM3M4LNWYOZDRD2BJFANCNFSM4KXGL4EA>.
|
Well the focus is left in the SCM view, it just jumps to the Tree container. Idealy the focus should be left in the same section of the view. @joaomoreno |
In short: I should be able to navigate in the SCM viewlet and press a key to stage / commit a change and the focus should remain in the SCM viewlet.
Enter currently opens the change and moves focus. I think that is fine, but we could have a shift + enter or something like that for stage / commit and keep focus.
A bit longer from @ndarilek
Sometimes I make several sets of changes, and want
to split them into logical commits. It can be hard to limit a set of
changes to a single logicl commit because often they need to be tested
together, and one won't make much sense if another is impractical or
unneeded. Right now I:
Press Ctrl-Shift-G to jump to the VCS changes view.
Tab to my changes.
Find a change in the tree.
Press the Applications key.
Arrow down to Stage Changes.
Press Enter.
Repeat 4-6 a few times...
Is it possible to stage changes just by pressing Enter on an item? That,
to me, seems most logical, with Discard and other operations remaining
reachable through the context menu. More often than not, I'm in this
view wanting to stage changes.
Yes I can set up Smart Commit to stage everything, but I've already
accidentally committed secrets that way. :) Yes I can group untracked
files and not Smart Commit those, but that took a bit of digging to set
up. I just think that the default in this view will almost always be to
stage the currently-selected change, so Enter should do that, though I
certainly won't bikeshed it if there are good reasons not to do this.
Just felt like I had to dig a git to find this, and VSCode nudged me
toward a behavior that, in its default configuration, probably isn't
wise (at the very least, Smart Commit shouldn't default to also adding
untracked files.)
The text was updated successfully, but these errors were encountered: