Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Selection to Next Find Match selects an extra match #57453

Closed
tylerstillwater opened this issue Aug 28, 2018 · 7 comments
Closed

Add Selection to Next Find Match selects an extra match #57453

tylerstillwater opened this issue Aug 28, 2018 · 7 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug editor-find Editor find operations important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@tylerstillwater
Copy link

Issue Type: Bug

When using "Add Selection to Next Find Match" (default cmd+d on mac) to select the word under the cursor, a second match of the same word is selected when the search panel is open.

Video demonstration: http://cloud.stillwater.me/07969533b382/Screen%20Recording%202018-08-28%20at%2001.41%20PM.mov

VS Code version: Code 1.26.1 (493869e, 2018-08-16T18:31:26.156Z)
OS version: Darwin x64 17.7.0

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz (8 x 2600)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: unavailable_software
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 3, 3, 4
Memory (System) 16.00GB (0.20GB free)
Process Argv /Applications/Visual Studio Code.app/Contents/MacOS/Electron
Screen Reader no
VM 0%
Extensions (26)
Extension Author (truncated) Version
apib Jar 0.0.1
close-all ben 1.0.2
better-toml bun 0.3.2
solargraph cas 0.17.6
sql-formatter cym 1.0.2
pgsql dou 0.1.3
gitlens eam 8.5.6
json-tools eri 1.0.2
center-editor-window kai 2.1.1
graphql-for-vscode kum 1.12.1
python ms- 2018.7.1
azure-account ms- 0.4.3
cpptools ms- 0.18.1
Go ms- 0.6.88
vsliveshare ms- 0.3.577
incrementor nms 0.1.0
vscode-subword-navigation ow 1.2.0
vscode-docker Pet 0.1.0
ruby reb 0.20.0
partial-diff ryu 1.3.0
vscode-sql-beautify sen 0.0.4
vscode-fileutils sle 2.10.3
rewrap stk 1.9.1
selectline-statusbar tom 0.0.2
vscode-todo-highlight way 1.0.4
change-case wma 1.0.0
@vscodebot vscodebot bot added editor editor-find Editor find operations labels Aug 28, 2018
@alexdima alexdima added the bug Issue identified by VS Code Team member as probable bug label Aug 29, 2018
@alexdima alexdima added this to the August 2018 milestone Aug 29, 2018
@alexdima alexdima added the important Issue identified as high-priority label Aug 29, 2018
@alexdima
Copy link
Member

@tylerb Thank you for reporting it! I also noticed this a couple of times and it was driving me crazy because I couldn't come up with reproducible steps.

@alexdima
Copy link
Member

Steps:

  • open find widget
  • click on a word
  • press ctrl+d or cmd+d
  • two words are selected when only one should have been selected

kapture 2018-08-29 at 15 09 47

@alexdima
Copy link
Member

alexdima commented Aug 29, 2018

fyi @sandy081 I believe this got introduced with 83713d3 where before the find widget would react only to findInput.onInput, after the change the find widget reacts to all findInput.inputBox.onDidChange, including in the case that the find widget sets the search string programmatically.

@sandy081
Copy link
Member

@alexandrudima Sorry for that. Thanks for the fix

@tylerstillwater
Copy link
Author

@alexandrudima You're welcome for the report. Thanks for the fix! Is it possible to get this fix into my local environment right away? It is a constant nuisance for me.

@alexdima
Copy link
Member

@tylerb It will come out with tomorrow's Insiders build

@tylerstillwater
Copy link
Author

Excellent. Thanks!

@octref octref added the verified Verification succeeded label Aug 30, 2018
joaomoreno pushed a commit that referenced this issue Sep 13, 2018
…d_branch_name_validation

* Microsoft/master: (4802 commits)
  Fixes #57415: autoSurround - rename "always" to "languageDefined"
  debug: skip over %0
  explorer view: cut down delay time till progress from 3.2s to 1.2s
  file workspace suffix is empty string
  Revert "debug: do not send terminate to EH debugging"
  Fixes #57411: Rename `autoWrapping` to `autoSurround` to avoid confusions related to text wrapping
  Fixes #57453: Avoid thinking the user typed in the find input when setting the search string value
  Synchronisation notification: - Show extension being synchronised - Delete the downloaded extensions
  [html] fix tests
  debug: do not send terminate to EH debugging
  webpack - let build fail when webpack generates an error or a warning
  [html] update service. Fixes #57445
  node-debug@1.27.6
  more complete fix for #57483
  fix #57351
  fix #57483
  fixes #56015
  dispose of RunOnceScheduler properly
  Fixes microsoft/monaco-editor#1021: Use ProviderResult in modes.ts
  fix #55607
  ...
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug editor-find Editor find operations important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants