You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This does not seem to be a duplicate of any of the bugs above. The example above contains a rather long regex, but even with very simple ones you can verify that the replace is broken as soon as a \n is in the regex:
It seems that when we search in multiple files using a regex that contains the "\n" sequence, we cannot use the captured groups in the replace field:
Steps to Reproduce:
Multiline search with **non-**working replace ($1 & $2 are not replaced by their corresponding group)
Multiline search with working replace ($1 & $2 are correctly replaced by their corresponding group)
The text was updated successfully, but these errors were encountered: