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.

Sign up for GitHub

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

Jump to bottom

Eagerly show tab or Preview Editor when using "Quick open" #11355

Closed
wprater opened this issue Aug 31, 2016 · 3 comments
Closed

Eagerly show tab or Preview Editor when using "Quick open" #11355

wprater opened this issue Aug 31, 2016 · 3 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Milestone
Backlog

Comments

@wprater
Copy link
Contributor

wprater commented Aug 31, 2016 •
edited
Loading

When using Quick Open or editor stack ctrl+tab, the tab should be eagerly be selected so a visual context of the content can be seen below the quick open view pane.

While navigation the view with your arrow keys, if selected editor tabs were open, they would be switched to, hitting escape would return to the tap you initiated the action on, hitting return would in effect keep you on the tab that was being eagerly shown (through open tabs or the Preview Editor).

This is very helpful to find the file you're planning to open. It's heavily used feature of mine from ST3.

image

  • VSCode Version: 1.5 insider
  • OS Version: macOS

refs: atom/fuzzy-finder#5
@bpasero bpasero added the feature-request Request for new features or functionality label Sep 1, 2016
@bpasero bpasero added this to the Backlog milestone Sep 1, 2016
@bpasero bpasero removed their assignment Sep 1, 2016
@bpasero
Copy link
Member

bpasero commented Sep 1, 2016

Thanks for reporting this issue. Please use the issue search next time to see if there is a duplicate already. In this case, the issue has already been reported.

@wprater
Copy link
Contributor Author

wprater commented Sep 1, 2016

Certainly, I did some searching, but must have used the wrong terminology. Shall I remove this one, or cross reference another issue?

@bpasero
Copy link
Member

bpasero commented Sep 9, 2016

#8939

@bpasero bpasero closed this as completed Sep 9, 2016
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 9, 2016
@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.
Assignees
No one assigned
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@wprater @bpasero @dbaeumer