Eg try addExcludePattern("*"). That should exclude everything, right? ruleset.getExcludePatterns() even contains the string afterwards. But no, we expect a regex, this one is invalid, and that's silently ignored later by the file filter:
Invalid patterns should be reported to the user, preferably when they build their ruleset. For compatibility on master we can log and ignore them, but for 7.0.0, it would be best to report a warning/error in RulesetBuilder, and make RulesetBuilder throw the PatternSyntaxException.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4