grc VS lnav

Probably not as efficient, but I've been happily using grc [0] for the past several years. It handles simple rules quite well - beyond the basic info/debug/error coloring I use it for QOL such as different colors for even/odd timestamps and highlighting decimal places in large numbers.

[0] https://github.com/garabik/grc

A fairly simple program which only colorizes is grc. I wrote acolor in a similar vein, but it uses arbitrary programs/scripts instead of pure regex, and I've only written support for the programs I use, so no tcpdump. Don't use it unless you want to write your own colorizing scripts (if you do, please contribute!)

You may want to check https://github.com/garabik/grc

You'll probably appreciate grc.

There's this, which is a more modern dig, with color output, among other things: https://github.com/ogham/dog

There's also stuff like this, which will postprocess & color output from any command: https://github.com/garabik/grc, or https://github.com/armandino/TxtStyle

I also found grc and wrote my own conf.latexmk:

Conversely if you want to add color to a command, I have found Generic Colorizer to be useful: https://github.com/garabik/grc

Last few streams I was working on a re-implementation of grc with more modern Python syntax and updated packaging meta-data.

See https://lnav.org for a powerful mini-ETL CLI power tool; it embeds SQLite, supports ~every format, has great UX and easily handles a few million rows at a time.

The code base seems like a good reference as a small Python project.

My fav option in this class of apps: https://lnav.org/ It lets you use journalctl with pipes as requested here: https://github.com/Textualize/toolong/issues/4

For local development, I cannot recommend lnav[1] enough. Discovering this tool was a game changer in my day to day life. Adding comments, filtering in/out, prettify and analyse distribution is hard to live without now.

I don't think a browser tool would fit in my workflow. I need to pipe the output to the tool.

[1] https://lnav.org/

It looks like they run an SSH server inside a Docker container defined by this Dockerfile [1]. This uses the ForceCommand directive in the sshd_config file to ensure that a specific command is run when a user connects (rather than the user connecting directly to a shell).

Depending on whether the user connects as the `playground` or `tutorial1` user they interact with a bash script that is either [2] or [3].

[1]: https://github.com/tstack/lnav/blob/master/demo/Dockerfile

[2]: https://github.com/tstack/lnav/blob/master/docs/tutorials/pl...

[3]: https://github.com/tstack/lnav/blob/master/docs/tutorials/tu...