lnav VS tig

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...

Related but I use tig, a TUI, a lot to examine the state of my working tree and index and stage/unstage/reset changes piecemeal. It works great.

I'd like to plug [tig](https://github.com/jonas/tig) for those who don't use emacs. I see lazygit recommended here too, but I've been using tig for years now and love it's simplicity.

Try tig

I'm normally a CLI git (and tig) user.

Sometimes when I work in command line I use tig (https://jonas.github.io/tig/). There is also similar tool lazygit (https://github.com/jesseduffield/lazygit)

And you accidently open a git TUI

tig +My custom command to fix MR comments by quickly editing an old commit's changes at the time when that commit was created. (Like a more controlled git-absorb that explicitly selects a commit to fixup and therefor avoids rebase-conflicts when squashing)

today I looked at tig which is a nice text based GUI, and I think I will never use git log again :-)

If you are looking for more interactivity while remaining on the commandline, have you looked at Tig? Tig has a view for browsing refs, and you can sort by date.