searchf

Utility program to interactively search keywords in text files. Works in terminals thanks to curses.

Installation

pip install searchf

Requirements:

Python 3.6 or greater
Terminal with color support (ie. TERM=screen-256color or TERM=xterm-256color).

Features

Filters can either include or exclude file content
Filters can persist to disk
Multiple highlight and colorization modes (press h to cycle through all modes)
Color palettes (press c to cycle through all palettes)
Various other display modes (l toggles line numbers visibility, k toggles line wrapping, ...)
Multiple views (press 1, 2, 3 to switch) with possibility to pass filters of one view to another view (try !, @, #)
Common search key bindings (/, then n for next, p for previous)
Common key bindings to scroll up/down pages or goto line
Terminal resizing

Usage

searchf <FILE>

Press f to enter keyword in a new filter
Press ? for help

Press ENTER to define the first keyword of a filter and reveal only the lines containing that keyword. Press + to add another keyword to the current filter in order to further narrow down the lines currently displayed.

A filter is a list of keywords that a line must contain to match and get highlighted in a specific color. By defining multiple filters, you can reveal more content of the file. By default, lines not matching any filter are hidden, but you can progressively reveal context surrounding matching lines by pressing m multiple times, all the way to the whole content of the file. Filters can also be used to filter out content you do not want to see (press x to toggle this mode).

Why?

This tool is born from my need to interactively search into log files, with the ability to backtrack when hitting dead ends (hence the use of push/pop of filter and keyword), and to go down some exploratory paths on the side (hence the support of views). I use it most when I'm not fully aware of what I am searching for...

To be more specific, I often have to dig into build log files, which are a raw aggregate of many heterogenous sources (numerous compiler output, deployment scripts, test run and results, ...) resulting in rather unstructured output. The only commonality being that everything is more or less line-oriented. When a build failure occurs, searchf helps me find hints of the root cause which can be hiding about anywhere.

So this tool ends up making little or no assumption on the input file, which can be anything, unstructured and heterogenous, as long as it is line oriented.

Development