-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Search results need more space than the side bar allows #9435
Comments
search results need a separate tab, at least as an option. Current space is just too crowded - file name, file path, and results to make complete sense. |
+1, absolutely, couldn't agree more. |
Even text wrapping would be nice, I always find myself resizing the sidebar when searching. But a seperate tab is preferred, similar to Atom or Sublime. |
I was wondering if this feature would be coming along anytime soon? |
Need to add a feature to search for files within a directory |
Would love it too! Thanks |
As soon as this lands I'll be able to switch from Atom to VSCode! 👍 |
From tomorrow's insiders it is possible to put the search viewlet into the panel area using the setting |
@isidorn Is there a picture to see how it looks now (for those who aren't using insider's build)? |
Is there a way to add a keyboard binding to dismiss the search panel with escape? I got...
But I'm missing the when clause. Is there something like |
I believe that often, search results need more horizontal space to be truly useful than the sidebar allows, unless you expand the sidebar very wide (which then means less room for open files, and requires you to manually resize it bigger and smaller when going between search and editing, if you like to have the file tree open when editing).
My suggestion would be that search should have the option to display the results in a new tab, in a similar way to Atom or Sublime, or alternatively, the search pane could be relocatable to the bottom of the screen, so it would gain horizontal space in exchange for vertical.
The text was updated successfully, but these errors were encountered: