Different default keyboard shortcut for searching in code window and in terminal

[amdp]

When someone works on a code and the terminal/debug window frames at the same time, usually it's needed to search into the code window without clicking on the code frame itself, so when issuing commands in the terminal we find ourselves searching in the the wrong frame because we are typing and we don't want to click on the code frame and get back to the keyboard. If we had a default shortcut (the standard one, like cmd/ctrl + F) to search the code and another one (like cmd/ctrl + shift + T) for the terminal/debug frame, that problem wouldn't arise.
A little message will notify the user the first time that the standard shortcut works directly in the the code frame and not in the terminal/debug/and-so-on ones.

[albertosantini]

Well, interesting UX case.
The find form is open in different places and the context should be clear: editor or terminal.

Toggling off (Ctrl+J) the terminal, it may mitigate starting a search in the wrong context.

If you are "audacious", you may change the key binding for the terminal finding.

Type Ctrl+K Ctrl+S (or F1 and Preferences: Open Keyboard Shortcuts) to open keyboard shorcuts:

Search Terminal: Focus Find and set your preferred shortcut.

Hope that helps.

[amdp]

I saw it but in a hurry and thought it was a way to focus on the Terminal. Perfect answer, you made my day, thanks!