"Find in selection" shouldn't be the default

The feature may be logical and consistent, but that doesn't mean anybody wants it ;)

It would be just as logical and consistent, though different, if Sublime just left "In Selection" set to the last used state. That way, if I'm doing a job where I need to "Find In Selection" a lot, I know it'll stay selected all evening (until I manually untick it again)

Love the program, by the way. I feel a bit guilty leaving these complaints.

I run into the same problem. I frequently do stuff like: select a block of text, copy it, then find to jump to the place where I want to paste it, then I'll edit it as appropriate for the new location. Whenever I do this in Sublime, I end up bumping into this "find in selection" default. I know everyone wants different defaults, which requires taste on your part, but I'd be happy with a config flag.

We aren't the only people who find this weird:

http://twitter.com/#!/ericflo/status/112991059503616000

http://twitter.com/#!/ericflo/status/112991902911037440 

I wouldn't mind this behavior if there were a keyboard shortcut that I could use from within "Find" to clear the selection. Is there one?

  { "keys": ["alt+c"], "command": "toggle_case_sensitive", "context":
     [
       { "key": "setting.is_widget", "operator": "equal", "operand": true }
     ]
   },
   { "keys": ["alt+r"], "command": "toggle_regex", "context":
     [
       { "key": "setting.is_widget", "operator": "equal", "operand": true }
     ]
   },
   { "keys": ["alt+w"], "command": "toggle_whole_word", "context":
     [
       { "key": "setting.is_widget", "operator": "equal", "operand": true }
     ]
   },
   { "keys": ["alt+a"], "command": "toggle_preserve_case", "context":
     [
       { "key": "setting.is_widget", "operator": "equal", "operand": true }
     ]
   },

I end up most of the time wondering why nothing is found as I type, then realize that this option is enabled. The fastest way I have to fix the situation without using the mouse is to press ESC twice (once to stop finding, once to clear the selection) and then do Cmd-F again.

This is rather counter-productive.

This continually bugs me too. I’m on a Mac, and a very common use pattern that works everywhere is ⌘E to mark the selection as the text to find, then ⌘G to find next. But in ST2, this only works some of the time; at other times it tries to “find in selection” (and the text to find *is* the selection!). I haven't yet been able to determine the circumstances that lead to it working normally or with the incorrect “find in selection” behaviour.

In my user sublime-keymap file, I use:

    { "keys": ["super+f"], "command": "show_panel", "args": { "panel": "find", "in_selection": false } }

So command-F never enables "find in selection" mode

I use "Find in Selection" all the time, though I do agree that find highlights words and that makes it annoying. In ST3 you can toggle find in selection by going to preferences and changing the option "auto_find_in_selection" to what you want.