Nico Rikken

Two remaining suggestions for the future: - Include source code line numbers of the finding. Requires keeping track of this information when detecting - How best to deal with edge-case...

I'm now trying to validate with the [errorformat library](https://github.com/reviewdog/errorformat): `errorformat "%f: %m"` It seems it cannot succesfully parse the output of files with spaces and colons: ``` /tmp/pytest-of-nico/pytest-44/fake_repository14/invalid-license.py|| bad license...

I originally had a test with a filename with colons, but this was causing errors on Windows. I removed it.

The issue of using files with spaces seems to be an issue with the `errorformat` library: https://github.com/reviewdog/errorformat/issues/97 I don't think reuse-tool needs to escape filename output as there is already...

I was thinking the same thing. Also, my company name 'Alliander' triggers Prosebot. So rather than having to add it as an exception to all repositories, it would be nice...

I have the same issue for the Sonos Beam, using HDMI ARC. It seems that the node-sonos project has gotten support for line-in in version v0.20.0 https://github.com/bencevans/node-sonos/issues/148#issuecomment-354999615

Fair enough 👍 Maybe a separate GitHub account can be created to prevent access into the other Lynis repo's? I added an upstream Galaxy ticket, hoping to change things for...

Indeed, but I'd like to have a default task provided for this common use-case. Otherwise many people will be writing the same lines of code.

@ldez but would that make any difference regarding highlighting? Maybe we can keep both lists, and if not matched, fall back to general matching? Or will we than fail on...

My mistake, I assumed their behavior would be similar (end of line). Thanks for the clarification. Issue has just been reopened.