30

I find the new "quick find" dialog hard to use:

  1. It's difficult to see whether "Match case" or "Match whole word" are selected, especially when the editor is in focus.
  2. I find "Aa" harder to comprehend than "Match case", and "Ab" harder to comprehend than "Match whole word".
  3. The keyboard shortcuts to select Match case/whole word are only visible in the tooltip.
  4. The dialog is no longer moveable.

I know about remapping "Find in Files" to Ctrl+F, but then there are too many clicks to search the current document vs all files.

Jon
  • 5,275
  • 5
  • 39
  • 51
  • 1
    I was really hoping to see an answer here. I'm in the same boat. – James R. Apr 07 '15 at 14:09
  • problem is should only one option to be chosen, once it's ON, no matter how you click it, always ON. :( – Jeb50 Mar 14 '18 at 21:10
  • 1
    The quick find window is just annoying; it has keyboard handling problems and keeps forgetting regular expressions. I opened bug requests with Microsoft. Not everything in the new quick find dialogue is bad, though. I would like to see the layout of the new dialog and the general handling of the old one (dockable). and, clearly, no bugs. – cskwg Apr 21 '20 at 09:09

4 Answers4

3

Its the same shortcut, CTRL+SHIFT+F However, seems like it is changed a lot.

  1. By default, it will show "ALL" results in a new window
  2. You have click on Find "Find Next" to find within open document.

I am also used to use that old dialog. I am not feeling comfortable with this new dialog. Wish I could bring back that old dialog somehow.

thanks Sameers

Sameers Javed
  • 342
  • 2
  • 5
  • 16
2

There doesn't seem to be a way to accomplish this in Visual Studio per se, however if you install AutoHotkey, you can simulate similar behaviour to VS2010 (also a favourite version of mine).

The AHK script I made for myself is here: pastebin.com/M0fVTzLr

It assumes you have CTRL-SHIFT-F and CTRL-F mapped to "Find in Files". So when you hit CTRL-F, for example, "Find in Files" dialog appears, and the AHK script sets the "Look In" to "Current Document". Also, when you press ENTER, it doesn't do a "Find All" but does a "Find Next". To perform a real "Find All", you'll have to hit ALT-A.

In addition, I made SHIFT-ENTER perform a "Find Previous".

So basically, with this AHK script, you just hit CTRL-F, type your text to find, the hit ENTER to find it, and SHIFT-ENTER to find previous.

If you wish to simulate the behaviour of closing the Find in Files dialog after you hit ENTER and it does the first find, then change the line:

Enter::SendInput !f

to:

Enter::
  SendInput !f
  Wait 100
  SendInput {esc}
  Return

Note: It will always set the "Look In" box to "Current Document", even if you have text selected. However, you could always set up another hotkey, such as CTRL-ALT-F, to do the same as above but set the "Look In" box to "Selected Text". As CTRL-F forces it back to "Current Document", you don't have to worry about what the default will always be. :)

ingredient_15939
  • 3,022
  • 7
  • 35
  • 55
-1

Ctrl-Shift-F is a different dialog than Ctrl-F. It is the old dialog.

Chris Alonzo
  • 43
  • 1
-3

The shortcut for opening the find dialog is Ctrl + Shift + F.

Sunius
  • 2,789
  • 18
  • 30
  • 2
    No, that's the Find in Files dialog which I already mentioned as not being suitable. – Jon May 20 '14 at 06:32