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

Open in background hotkey should only activate if cursor is at end of line #14350

Closed
wprater opened this issue Oct 25, 2016 · 9 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@wprater
Copy link
Contributor

wprater commented Oct 25, 2016

  • VSCode Version: 1.7

The right arrow key used to open the selected quick open item in the background should only dispatch if the cursor was at the end of the line and not used with another modifier e.g. option or command/ctrl.

When navigating up/down through the list, the cursor should be placed to the end of the line. This behavior is similar to ST.

/cc @bpasero

Feel free to assign to me and comment regarding your feelings on the UX.

@bpasero
Copy link
Member

bpasero commented Oct 25, 2016

@wprater would it not make more sense to ask the user to hold a modifier key before opening a file in the background? the user might quickly arrow to the right and would not expect any editor to open.

@bpasero bpasero self-assigned this Oct 25, 2016
@bpasero bpasero added this to the October 2016 milestone Oct 25, 2016
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Oct 25, 2016
@wprater
Copy link
Contributor Author

wprater commented Oct 25, 2016

yeah, I think that is a valid approach as well. I was going with what ST had modeled. We cannot use the cmd or option modifiers as they are used to jump word boundaries. ST uses the end of line technique to prevent this, perhaps?

I have another idea for UX: when you first pull up the quick open widget, can we have no items selected until one hits down or starts to type?

@bpasero
Copy link
Member

bpasero commented Oct 25, 2016

Maybe we just do it if you press Alt key while using the arrow keys. It is less discoverable though.

No, we cannot change the auto selection, if we did, you would always have to arrow down after searching, that is very awful UX.

@bpasero
Copy link
Member

bpasero commented Oct 25, 2016

@wprater pushed a change to behave like Sublime, maybe you give it a swirl.

@wprater
Copy link
Contributor Author

wprater commented Oct 25, 2016

No, we cannot change the auto selection, if we did, you would always have to arrow down after searching, that is very awful UX.

the idea would be upon typing the first entry could be auto-selected. if none were found, nothing would be selected. you can still use the down arrow to navigate.

@wprater
Copy link
Contributor Author

wprater commented Oct 25, 2016

@wprater pushed a change to behave like Sublime, maybe you give it a swirl.

made a comment on your commit.

@Tyriar Tyriar added the verified Verification succeeded label Oct 27, 2016
@Tyriar
Copy link
Member

Tyriar commented Oct 27, 2016

@bpasero is this feature documented anywhere? I only just discovered it from this.

@wprater
Copy link
Contributor Author

wprater commented Oct 27, 2016

@Tyriar here is a PR, if that's helpful to you
#13925

@Tyriar
Copy link
Member

Tyriar commented Oct 27, 2016

/cc @gregvanl here's a poweruser feature that we may want to add to documentation?

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants