Logfile viewer and highlighter for Sublime Text 3
- Total 12K
- Win 7K
- OS X 4K
- Linux 2K
|May 26||May 25||May 24||May 23||May 22||May 21||May 20||May 19||May 18||May 17||May 16||May 15||May 14||May 13||May 12||May 11||May 10||May 9||May 8||May 7||May 6||May 5||May 4||May 3||May 2||May 1||Apr 30||Apr 29||Apr 28||Apr 27||Apr 26||Apr 25||Apr 24||Apr 23||Apr 22||Apr 21||Apr 20||Apr 19||Apr 18||Apr 17||Apr 16||Apr 15||Apr 14||Apr 13||Apr 12||Apr 11|
Logfile highlighter for Sublime Text 3.
This plug-in requires at least Sublime Text 3 Build 3065. Please download the correct sublime text version before using this plug-in.
This Sublime Text 3 plug-in automates some common tasks when opening logfiles: - Automatically makes the file read-only to prevent accidental changes. - Search for common patterns and highlight them (see chapter “Automatic highlighting”) - Set bookmarks on the highlighted lines to speed up inspection of the matches.
Supported file extensions
All files using the extension .log are automatically opened as logfiles. Any other file can be treated as a logfile by changing the syntax to “Logfile”.
This package should be installed using Package Control. Follow these steps to install LogView: - Make sure you're using the correct Sublime Text 3 version (see Requirements). - Install Package Control if you don't already have it. - Use Package Control to search for LogView and install the package.
Editing the logfile
You have to switch to the “Plain Text” syntax in order to edit the opened logfile. As soon as you're done editing the file, you can switch back to the “Logfile” syntax. The file will automatically be parsed again and set to read-only.
The LogView plug-in distinguishes three types of log entries: - errors - warnings - marks
Matching lines are marked with an icon within the gutter, too. If you only want the lines to have icons and no other hilighting should be performed set the
highlight_style parameter within the config file to
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.
||Scope used for marking lines containing a match of the error_filter regular expression.|
||Prefix for the number of lines containing a match of the error_filter regular expression. This can be used for I18N.|
||Scope used for marking lines containing a match of the warning_filter regular expression.|
||Prefix for the number of lines containing a match of the warning_filter regular expression. This can be used for I18N.|
||Scope used for marking lines containing a match of the mark_filter regular expression.|
||Prefix for the number of lines containing a match of the mark_filter regular expression. This can be used for I18N.|
||If this config option is set to true the reguluar expression set via
||Configures the style for marking the lines selected by the filters. Available styles are: fill, outline, underline and none. See default config for details.|
All configuration parameters can be set via the Preferences menu. Just open Preferences > Package Settings > Log View > Settings.