Debugging issues with over-greedy regexes about log-highlight HOT 5 CLOSED

Try this : [ "[^\\r\\n]*?ERROR:", "[\r\n]" ] instead of [ "^.*ERROR:", "[\r\n]" ], and remove all other regex lines.

from log-highlight.

Thanks.

Yes, if I disable all the other severity levels, the above works (doubling the backslashes) to catch the error line only. Adding the same thing for the WARN levels catches those too, except it results in them all landing on separated lines in the summary window.

Doing some experimenting, this also works: [ "^[\\w\\. ]+ERROR:", "[\\r\\n]" ], and is maybe more exact, but still results in the summary being separated.

So, it does look like this is a regex question. I'll change the issue title.

from log-highlight.

Out of curiosity, is each line in the summary window supposed to be separated from its neighbors with an extra line? e.g., the whole thing is double spaced: I'm not sure if that's intended behavior or not.

from log-highlight.

I put extra 1 line to separate them for summary.

from log-highlight.

Got it, thanks; I wasn't sure if that was expected behavior. Could you please mention that in the "Summary Output Panel" of the readme? I wasn't sure if I'd misconfigured things.

Thank you for the help.

from log-highlight.