Sorry about that.
Is there a command I can run to apply your in-house formatting automatically/retroactively?

EDIT: fixed.

@rebornix I believe I fixed the formatting issue. Any next steps you need from me?

I just tried checking out and building this PR, and it does not fix #60977 or #70306 for me. Even with "search on type" disabled, when I click into another editor it will still jump to the first instance of whatever is in the find box. And typing into the box causes the editor to scroll to the first instance of whatever I'm typing. Changed the wrong setting.

@briankendall Can you verify that you un-selected move on type, and not search on type?

There is an unrelated, pre-existing setting search on type that has no effect.

The reason I ask is that @rebornix confirmed it worked in #60977 (comment) , and this PR is the same as my original, just behind a setting, so I thought maybe you just ticked the wrong one.

Maybe the naming could be clearer.

@ultraGentle You're right, I changed the wrong setting! It is in fact working for me.

@rebornix I just made another commit:

• Debounces typing into the Find Widget

• This way, even users that do not disable moveOnType will avoid the editor auto-searching until they finish/pause typing -- which seems universally desirable.

• If you just want the moveOnType setting without debounce, please merge the previous commit instead.

--
Edit: I note that the build failed on my latest commit; so maybe just use the previous one for now, and treat the "debounce" as a proof of concept.

As always, I'd appreciate any feedback on what I need to do to get this successfully merged. Thanks for considering!

Any update on this getting merged?

Same, I'd love to have this

I haven't heard from @rebornix that any changes are necessary, and as far as I can tell, all testers have had positive experiences with no issues. Hoping this will make it into next month's update!

Ok that would be great, looking forward to it.

@adamreisnz , I think I implied that this will make it into the next release. If so, sorry -- that was just me hoping along with everyone else on this thread! I unfortunately don't have any insider info to share. I can't tell whether this is just pending, or has been dropped.

Excited and hopeful to have this merged.

I'm not sure what the deal is with radio silence from the VSCode team regarding this issue. I've already pinged the reviewer, with no response, and I don't want to be a squeaky wheel, so it's not clear to me what the way forward is. If I knew there were a problem, I'd fix it, but without any feedback I'm flummoxed.

It's very strange to me, since this is a small PR and it fixes a super annoying bug, but I know folks are busy, so maybe there just hasn't been time for them to re-review and merge? Or maybe there's something else holding it up?

The opacity here is a disincentive to contribute to other issues, since it feels futile to work on something if it's not going to end up in the final product. Not complaining, promise, just confused!

@rebornix would you mind reviewing this PR? It would really save us a lot of headaches with the cursor jumping to unexpected locations in the file.

Thanks @ultraGentle for your contribution! I tweaked the code a bit and merged into master, should be available in Insiders later this week.

@rebornix My pleasure!

Is this implemented? How can I enable this setting?

@TheInvoker Should be as of today or tomorrow. It's been in insiders edition for a month, so just waiting for 1.49 to be released. Setting is find > "moveCursorOnType" if I remember correctly.

We're finally there!

1.49.0 stable was released today with the setting
find > moveCursorOnType > set to false
which activates the desired behavior

Edit: Note that if you previously had global find clipboard set to false to avoid unexpected cursor jumping/highlighting when switching panes, you can now re-enable that setting, as moveCursorOnType > false fixes that bug.