search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
163.09k stars 28.82k forks source link

Setting editor.find.seedSearchStringFromSelection to Always does not always seed the Find Widget #200867

Open FastieSystems opened 9 months ago

FastieSystems commented 9 months ago

Type: Bug

editor.find.seedSearchStringFromSelection has always been set to "always" in my configuration, and the Find Widget shows the previous search string, nothing, or the selected text. The previous search string is the most common result. Inexplicably, Replace seems more reliable.

I have tried restarting VSC or saving and reloading files. The flawed behavior has been consistent since I first began using VSC.

This report is submitted pursuant to a request from amunger.

VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z) OS version: Windows_NT x64 10.0.19045 Modes:

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz (4 x 3498)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|undefined| |Memory (System)|15.88GB (6.47GB free)| |Process Argv|--crash-reporter-id 9ebebe49-1c05-4122-ac9e-3e60ceb63b56| |Screen Reader|no| |VM|0%|
Extensions (10) Extension|Author (truncated)|Version ---|---|--- vscode-css-formatter|aes|1.0.2 vscode-intelephense-client|bme|1.10.2 vscode-mysql|for|0.5.0 vscode-htmlhint|HTM|1.0.5 remove-break-lines|jal|1.0.0 vscode-apache|mrm|1.2.0 live-server|ms-|0.4.13 powershell|ms-|2023.8.0 sftp|Nat|1.16.3 change-case|wma|1.0.0
A/B Experiments ``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vslsvsres303:30308271 vserr242cf:30382550 pythontb:30283811 vsjup518:30340749 pythonptprofiler:30281270 vshan820:30294714 vstes263:30335439 vscoreces:30445986 vscod805cf:30301675 binariesv615:30325510 bridge0708:30335490 bridge0723:30353136 vsaa593:30376534 pythonvs932:30410667 py29gd2263:30899288 vsclangdc:30486549 c4g48928:30535728 dsvsc012:30540252 azure-dev_surveyone:30548225 2e4cg342:30602488 89544117:30613380 2i9eh265:30646982 showlangstatbar:30737416 0bi6i642:30917235 fixshowwlkth:30771522 showindicator:30805244 pythongtdpath:30769146 i26e3531:30792625 welcomedialog:30910333 pythonnosmt12:30797651 pythonidxpt:30866567 pythonnoceb:30805159 asynctok:30898717 dsvsc013:30795093 dsvsc014:30804076 dsvsc015:30845448 pythontestfixt:30902429 pyreplss1:30897532 pythonmypyd1:30879173 pythoncet0:30885854 h48ei257:30885898 pythontbext0:30879054 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 aa_t_chat:30882232 dsvsc019cf:30917260 ```
FastieSystems commented 6 months ago

Upon experimentation: If the search text selected for find/replace contains a newline, the text will not be inserted into the find field. Otherwise, it will.