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
search string not seeded from selection #38854
Comments
This is currently by design. That setting only affects the editor find widget. For search, I want to only put the text in the search viewlet when someone uses cmd+shift+f from the editor. |
I searched exactly for this and I find it closed :|
|
Trying to make everyone happy :) In Sublime, there is just one setting that controls this for local and global find. I think it's a valid request but it's different in vscode because there are more ways to activate the search viewlet, which I think shouldn't copy the selected text. |
I understand about the one setting, I only searched on Google and found this because it stopped working like it did before the update. After searching in the preferences I found this setting which matched the problem :) Until the update it worked like this: I have the Explorer panel open > I select a text in the editor > click on the Search icon to open Search panel > selected text from Editor is inserted by VS Code automatically into search box from Search panel Since last update, a ~week ago, it doesn't insert the selected text int the search box and I must do 3 more steps in order to perform a search: copy selected text, select previous text in search box, paste copied text. |
I changed it in the last update on purpose because I found it annoying when the search viewlet would take the selected text just because I wanted to check previous search results. I think it should take the text in some cases but not others. |
If possible, it would be good to have it as a preference. |
Steps to Reproduce:
NB made sure the following was set:
"editor.find.seedSearchStringFromSelection": true
Reproduces without extensions: Yes/No
The text was updated successfully, but these errors were encountered: