Change Details

The problem is, that there is no possibility to use newline options within regular expressions doing insource searches using Special:Search. Maybe it's forgotten when programming the regex machine. Solution: You can use the escape sequence "\n' doing a search with newline within regular expression. It's useful to find and then repair LINT errors and making other corrections that go beyond one source code line. Thanks a lot, Martin ... Example: ```insource:/foo bar\ncode red/``` should find in the source code ```foo bar code red```

The problem is, that there is no possibility to use newline options within regular expressions doing insource searches using Special:Search. Maybe it's forgotten when programming the regex machine. Solution: You can use the escape sequence "\n" doing a search with newline within regular expression. It's useful to find and then repair LINT errors and making other corrections that go beyond one source code line. Thanks a lot, Martin ... Example: ```insource:/foo bar\ncode red/``` should find in the source code ```foo bar code red```

The problem is, that there is no possibility to use newline options within regular expressions doing insource searches using Special:Search. Maybe it's forgotten when programming the regex machine. Solution: You can use the escape sequence "\n'"\n" doing a search with newline within regular expression. It's useful to find and then repair LINT errors and making other corrections that go beyond one source code line. Thanks a lot, Martin ... Example: ```insource:/foo bar\ncode red/``` should find in the source code ```foo bar code red```