Change Details

The "([^: \\t]+):" does not match strings with white space. While this reduces the chance of wrong matches, it also excludes valid ones for paths with white space in them (like on new KDE CI). The different regex for the different tools are a bit inconsistent on that matter, so as consistent solution whitespaces in paths are supported. Separate commit for the fixes of the missing double escape for \t (?)

The "([^: \\t]+):" does not match strings with white space. While this reduces the chance of wrong matches, it also excludes valid ones for paths with white space in them (like on new KDE CI). The different regex for the different tools are a bit inconsistent on that matter, so as consistent solution whitespaces in paths are supported. Tests are adapted to test with both paths with spaces and paths without (for now only unix-style, given the patterns currently used).

The "([^: \\t]+):" does not match strings with white space. While this reduces the chance of wrong matches, it also excludes valid ones for paths with white space in them (like on new KDE CI). The different regex for the different tools are a bit inconsistent on that matter, so as consistent solution whitespaces in paths are supported. Separate commit for the fixes of the missing double escape for \t (?)Tests are adapted to test with both paths with spaces and paths without (for now only unix-style, given the patterns currently used).