The cursor waits at your terminal, blinking like a signal. You type lnav and stop—shell completion could take you further, faster.
Lnav shell completion is not decoration. It is precision. With it, you navigate logs without guessing commands or flags. Tab once, and the right option appears. No wasted keystrokes. No hunting through docs.
Lnav provides shell completion scripts for Bash and Zsh. To enable them, first check if your system includes completions in its package. Many distributions install them with lnav, but if not, you can generate them yourself. Run:
lnav --completion
Save the output to a file inside your shell’s completion directory. For Bash, this might be /etc/bash_completion.d/lnav. For Zsh, place it under a directory registered in fpath. Reload your shell or source the file directly:
source /etc/bash_completion.d/lnav
From here, completion works instantly. Type lnav and hit Tab to see supported options—filters, formats, queries. No lag. No syntax errors.
Efficient shell completion matters for log analysis workflows. When you run advanced SQL queries inside lnav, completion keeps input accurate. When you switch between multiple log formats, it saves steps. This leads to tighter loops, cleaner results, and less mental overhead.
Use completion as part of a repeatable setup. Pair it with an .lnav config that loads custom views on start. Automate loading through scripts. The goal: faster log inspection every time, with no friction.
If your team handles critical logs, setting up shell completion in Lnav is essential. It removes uncertainty and accelerates troubleshooting.
Want to see this workflow go from zero to live in minutes? Try it with hoop.dev and watch Lnav shell completion turn raw logs into immediate insight.