Vscode: Add find and replace in files/project
ctrl+shift+f dialog does not feature a project-level find and replace.
Tyriar
All 60 comments
:+1:
bpasero
on 30 Dec 2015
:+1: Required for me!
philipgiuliani
on 21 Jan 2016
:+1:
tschwartz
on 2 Feb 2016
:thumbsup:
bunterWolf
on 11 Feb 2016
+1
morrismukiri
on 12 Feb 2016
๐
UPDATE 6/21/16
What sense does it make to thumbs-down posts from before reactions were introduced in March 2016?
Thumbs down if you think you think you should stop trolling and start contributing.
ianwesterfield
on 17 Feb 2016
Please.
jaysylvester
on 28 Feb 2016
:+1:
be5invis
on 7 Mar 2016
There were 6 distinct :+1:'s on https://github.com/Microsoft/vscode/issues/773 which was closed in favor of this.
Tyriar
on 7 Mar 2016
Finally...
เผผ ใค โ_โ เผฝใค PRAISE CODE เผผ ใค โ_โ เผฝใค
be5invis
on 7 Mar 2016
What is this still doing in the backlog? There are more important features? [:
I'm currently using another editor just for the cases when I have to do a mass find-replace for refactoring.
+1
Roustalski
on 15 Mar 2016
+1
tjosbon
on 17 Mar 2016
:+1:
johnsoncze
on 21 Mar 2016
+1
JeandeCampredon
on 1 Apr 2016
+1
christianmenz
on 9 Apr 2016
+1
danhowitt
on 9 Apr 2016
+1 :+1:
I'm in the same situation of having to use something else solely for "replace all" in multiple files :(
dgghita
on 13 Apr 2016
Ok let's try with product pain:
https://productpains.com/post/visual-studio-code/replace-all-occurences-in-multiple-files-of-a-project
JeandeCampredon
on 13 Apr 2016
@JeandeCampredon To be fair, since it's been assigned, it does look like this is being worked on now :)
dgghita
on 13 Apr 2016
The correct Another place for this is User Voice: https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/11329521-find-and-replace
Please add votes there (also).
ashes999
on 29 Apr 2016
@ashes999 both user voice and :+1:'s on GitHub are useful.
Tyriar
on 29 Apr 2016
@Tyriar if you look at user voice, MS employees actually respond to and act on those. So it's a matter of getting enough momentum there. (I don't know how closely they look at GitHub issues.)
ashes999
on 29 Apr 2016
:+1:
luisrudge
on 1 May 2016
:+1:
ClementVidal
on 9 May 2016
+1
krasi0
on 10 May 2016
@ashes999 I'm one of the said Microsoft employees :smiley:
I think if GitHub reactions were around at launch then we wouldn't have needed user voice. Currently both lists are used to find what features are highly desired by the community.
Tyriar
on 12 May 2016
Please add this feature
tsirolnik
on 16 May 2016
+1
ruspaull
on 17 May 2016
+1
mevdschee
on 17 May 2016
+1
VRspace4
on 18 May 2016
+1
johnfredrik
on 18 May 2016
+1
bogosts
on 18 May 2016
+1
olivierl
on 20 May 2016
Hi all, prefer :+1: reactions on the original issue comment as that helps us with prioritization.
Tyriar
on 20 May 2016
+1
JoeCostanzo
on 25 May 2016
Can't believe you guys went past version 1.0 without this!
Makes me wonder if the editor has already a similar functionality that I'm not seeing??
cesarvarela
on 26 May 2016
@cesarvarela I agree. Maybe there is an extension or something. I tried looking and couldn't find one.
caseyhoward
on 26 May 2016
God, stop posting these +1's.
And wouldn't it be easy as calling the find&replace function over the found files?
I'll try looking it up
tsirolnik
on 26 May 2016
@tsirolnik it is as easy (or as hard) as that. It can be quite a task with matches spanning across a significant amount of files.
Tyriar
on 26 May 2016
:+1:
zpdDG4gta8XKpMCd
on 1 Jun 2016
:+1:
xtbe
on 2 Jun 2016
+1 this is a pain to do now. Also the file find/replace box covers the first line of code, very annoying!
TonyCurtisLives
on 2 Jun 2016
๐ ๐ ๐ ๐ ๐ ๐ ๐ ๐
gavinslilley
on 7 Jun 2016
+1 Probably one of the most important features to have... It makes no sense not to have it in.
shaneparsons
on 9 Jun 2016
This is the only thing keeping this editor from being my primary choice. It's a simple thing to implement but it saves SOOOOO much time.
ammario
on 19 Jun 2016
+1
dmiorandi
on 27 Jun 2016
+1 ๐
TamerZorba
on 27 Jun 2016
This is coming for June, stay tuned.
@sandy081 you deserve credit here.
bpasero
on 27 Jun 2016
Praise the mighty @sandy081 ๐ค๐
tsirolnik
on 27 Jun 2016
Implemented using #7602
sandy081
on 1 Jul 2016
And what about Global Replacing with RegExp captures?
Content: SomeTextAndStopKeyword
Find: (.*)AndStopKeyword
Replace: StopKeywordAnd$1
Expect: StopKeywordAndSomeText
Currently, I see it just replaces with a plain text StopKeywordAnd$1, while inline Search&Replace works just fine.
dazewell
on 12 Jul 2016
Why is Regex Replace supported on single file edition and not on multiples files, where it is really needed.
You may search with Regex, but not replace/substitute based on your regex conditions..
Furthermore, since preview is provided, there no risk of massive/unexpected changes
Other node based editor already implements it like Atom.
jacquelineth
on 13 Jul 2016
@dazewell @jacquelineth
There was no reason for not supporting it. I just pushed this feature today and is available from next insiders build. - https://github.com/Microsoft/vscode/issues/9010
Thanks
sandy081
on 13 Jul 2016
Cool!
Thanks, looking forward using it.
dazewell
on 13 Jul 2016
Just used it.... Awesome.
Thanks a lot!
jacquelineth
on 14 Jul 2016
Today I had an update but it doesn't seem to contain those changes. So, I'm still waiting.
But what about those hotkeys for turning on the RegExp mode and Whole Word mode and Case Sensitive mode for the Global Search?
dazewell
on 14 Jul 2016
@dazewell I think you're referring to https://github.com/Microsoft/vscode/issues/4719, please add a :+1: to show your interest in it.
Tyriar
on 14 Jul 2016
It is available in latest insiders build (not on stable).
sandy081
on 14 Jul 2016
@Tyriar thanks, that's exactly what I was talking about. Sorry for polluting this issue.
@sandy081 understood, thanks!
dazewell
on 15 Jul 2016
Why is it that VS Code limits find/replace to 999 occurences only?
repositorio-ultra
on 10 Feb 2017
Related issues
curtw
ยท
3Comments
shanalikhan
ยท
3Comments
borekb
ยท
3Comments
philipgiuliani
ยท
3Comments
lukehoban
ยท
3Comments
Most helpful comment
@ashes999 I'm one of the said Microsoft employees :smiley:
I think if GitHub reactions were around at launch then we wouldn't have needed user voice. Currently both lists are used to find what features are highly desired by the community.