Option for seeding find string from editor on ctrl + f

[Tekbr]

• VSCode Version: 1.10.0 - insider
• OS Version: Windows 10

-- Sorry for the English, I used Google Translator --

If I put the cursor on the word (start, middle or end of word) and press ctrl + f, that word is automatically placed in the search.

Is not that wrong?

The correct would be if I selected the word and then pressing ctrl + f it should appear in the search field.

[joaomoreno]

It's not really wrong. If you don't like it, we can make a setting for it.

[Tekbr]

Thank you João Moreno (@joaomoreno)

alexandrudima João Moreno (@joaomoreno) I compared it to other editors (Atom and Sublime). If there is person they like, maybe an option to turn it on and off.

[coreyfarrell]

To expand on the reporters description, the current behavior makes it oddly difficult to "find again". For example I just searched a Javascript file for the start of arrow functions ) =>, and removed the parenthesis from functions with a single parameter. After each edit I had to make sure I moved the editor cursor to empty whitespace before pressing Ctrl-F again, otherwise I had to retype my search value.

[joenoon]

I'm having the same issue that Corey Farrell (@coreyfarrell) explained. Here is my usual/desired workflow:

1. cmd+f, enter search term hit enter
2. esc to exit Find dialog on the current found
3. change text in editor
4. cmd+f again to try and find the next occurrence, except Find opens with whatever the cursor happens to be on

If anyone knows a way to work around this or just stop the editor from changing the Find that would be great.

[frostius]

Continued from #17562 as requested. That said, this is really about usablity of replace

If a multi-line selection is made and replace is invoked (ctrl-h):

• Default to find in selection
• Set find input value to last find|replace value
• Set focus to find input control (not replace)

Reasons:

• reduces keystrokes/clicks necessary to do a replace
• attempting to search for a multi-line string is a very rare use case (currently can't even see most of a multi-line find string)
• consistent with mainstream editors (MS office, visual studio, intellij, etc)

[tbfleming]

@mfrost66 I wish. At one point ctrl+f behaved something like that, but it confused OSX users.

[Tekbr]

-- Sorry for the English, I used Google Translator --

Peng Lyu (@rebornix) I found these new functions:

"editor.find.autoFindInSelection" and "editor.find.seedSearchStringFromSelection":

I did not understand their operation. Besides that, what I have reported is not happening.

My problem is:
1- Place your cursor over a word.
2- Press Ctrl + f.
3- The word goes to the field of research and I do not want to search it.

Now if I had selected the word and pressed Ctrl + f, then yes it should go to the search field.

[Tekbr]

Peng Lyu (@rebornix) Can you check and answer me, please?