Fix SelectionMatchFindAction to respect seedSearchStringFromSelection setting

[teoincontatto]

Summary

• Makes editor.action.nextSelectionMatchFindAction and editor.action.previousSelectionMatchFindAction respect the editor.find.seedSearchStringFromSelection setting
• Previously these actions hardcoded getSelectionSearchString(editor, 'single', false), always enabling the word-at-cursor fallback regardless of user configuration
• Now reads the setting and passes it through consistently, matching the behavior of StartFindAction and other find actions

Fixes #300085

Change

One-line change in SelectionMatchFindAction.run() (src/vs/editor/contrib/find/browser/findController.ts):

Before:

const selectionSearchString = getSelectionSearchString(editor, 'single', false);

After:

const seedSearchStringFromSelection = editor.getOption(EditorOption.find).seedSearchStringFromSelection;
const selectionSearchString = seedSearchStringFromSelection !== 'never'
    ? getSelectionSearchString(editor, 'single', seedSearchStringFromSelection === 'selection')
    : null;

Behavior by setting value

Setting	Before (broken)	After (fixed)
"always" (default)	Seeds from selection or word at cursor	Same (no change)
"selection"	Seeds from selection or word at cursor	Seeds from selection only
"never"	Seeds from selection or word at cursor	Never seeds

Test plan

• With "editor.find.seedSearchStringFromSelection": "always" (default): select text, Cmd+F3, paste replacement, Cmd+F3 again → picks up word at cursor (unchanged behavior)
• With "editor.find.seedSearchStringFromSelection": "selection": select text, Cmd+F3, paste replacement, Cmd+F3 again → continues searching previous term (fixed)
• With "editor.find.seedSearchStringFromSelection": "never": Cmd+F3 never seeds from editor (fixed)
• Same scenarios with editor.action.previousSelectionMatchFindAction

[Copilot]

Pull request overview

Fixes SelectionMatchFindAction (next/previous selection match find actions) to honor the editor.find.seedSearchStringFromSelection setting, aligning its behavior with StartFindAction and other find actions. Previously it hardcoded the word-at-cursor fallback regardless of user configuration.

Changes:

• Read editor.find.seedSearchStringFromSelection option in SelectionMatchFindAction.run().
• Skip seeding when set to 'never', and only enable word-at-cursor fallback when set to 'always'.

Show a summary per file

File	Description
src/vs/editor/contrib/find/browser/findController.ts	Replace hardcoded getSelectionSearchString(editor, 'single', false) call with logic that respects the seedSearchStringFromSelection setting.

Copilot's findings

• Files reviewed: 1/1 changed files
• Comments generated: 0