Persistent, saved filters in config

[nikess]

Often one has the need to filter log files for the same thing. E.g. warnings, or other domain specific things.

Currently one has to add these input filter regexes manually every time you open a log file.

Ideally these could be specified as global "favorites", or log format specific filters.

On opening a file, they would be disabled, but available. One would toggle them on in the usual way, as needed.

[tstack]

Many parts of lnav can be manipulated using the SQLite interface. In this case, you can create filters by inserting rows into the lnav_view_filters table. If you want to create these filters on demand, you can create an lnav script file and execute the script with the | hotkey. If you want them created on startup, you can put a SQL file in a format directory (e.g. ~/.lnav/formats/installed) with the statements to be executed.

As an example, the following SQL will create a disabled "OUT" filter for the log view that matches the phrase "noisy message":

INSERT INTO lnav_view_filters (view_name, enabled, type, pattern) VALUES ('log', 0, 'OUT', 'noisy message');

[piotr-dobrogost]

#811 would be handy here.

[tstack]

With the addition of the events mechanism, I think this should all be possible now.