From d6200f92858130cfd5005fa2d7d8fba88b8da94c Mon Sep 17 00:00:00 2001 From: FlashSystems Date: Sun, 1 Mar 2015 22:17:56 +0100 Subject: [PATCH] Added a paragraph about filter precendence to the readme. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 42ee1eb..1b20935 100644 --- a/README.md +++ b/README.md @@ -33,6 +33,8 @@ The LogView plug-in distinguishes three types of log entries: It is possible to set a regular expression for detecting every type of log entry within the configuration file. If a file is loaded (or the file type is changed to "Logfile") it is automatically processed and all lines, that contain matches to the configured regular expressions are automatically highlighted and bookmarked. This way it is possible to analyse logfiles much faster and find the relevant portions with the "goto bookmark" (F2) functionality. The line highlighting feature shows the critical areas in the logfile via the Minimap. Portions of the logfile with a high density of red or yellow marks may hint at a problem. +If more than one regular expression matches for a given line of the logfile all matches are counted. For highlighting the line the error_filter takes precedence over the warning_filter and the warning_filter takes precedence over the mark_filter. + The "error_filter", "warning_filter" and "mark_filer" regular expressions contain sensible defaults. None the less you should tweak them to match the logfiles you're frequently dealing with. # Configuration parameters