In situations in which I need to make massive replacements, I prefer to
use the command line. It's more flexible and less expensive in terms of
memory. In Linux I use a mix of "find", "while" and "perl" with regular
expressions. For example:
find my-app/ -name '*.java' \ | while IFS= read -r path \
do perl -p -i -e 's/foo/bar/g' "$path"
If I need multi-line support, I type "BEGIN { undef $/; }" before the
Perl's regular expression.
Of course, I usually make backups before.
I know this doesn't solve your problem with NetBeans, but it'll save you
a lot of time.
On 5/6/22 19:52, Bilu wrote:
/this is likely hardcoded, I think I remember seeing some runaway
limits in search code./
=> too bad
/you could run the same search/replace action multiple times, right?/
/ => /this /is what i was doing since the morning. it is not very
helpfull with remote folders like smb sharing (very slow)/
/
/
Le 06/05/2022 à 19:30, Michael Bien a écrit :
Hi,
this is likely hardcoded, I think I remember seeing some runaway
limits in search code.
you could run the same search/replace action multiple times, right?
-mbien
On 06.05.22 16:50, Bilu wrote:
Hello,
When Replacing in a large project i get: *the search was stopped
because the limit for number of matching files (500) was reached.*
Is there any propertie to override this behavior in the netbeans.conf?
Please advise. Same for the 5000 occurrences matches
