does bat support vi navigation ?

[noor-tg]

like less when click j will go up in page k down

[keith-hall]

By default bat uses less as a pager, so anything less supports should work as usual

[noor-tg]

I used oxlint --help | bat -p -l man but when I click j k . it just print the char. not moving up or down. this is why I wrote this post
same with vitest --help | bat -p -l man

[vingenerator-blip]

Yes, bat supports basic vi-style navigation when it runs through less, so you can use keys like j, k, and search commands easily. It’s simple and efficient kind of like using a VIN generator, where everything just works smoothly without extra effort.

[kinthaiofficial]

bat itself doesn't have interactive navigation — it's a pager-aware output tool, not an interactive viewer. For vi-style navigation with bat's syntax highlighting, the usual pattern is to use bat as the previewer and pipe to a pager that supports vi navigation.

Option 1: bat + less with vi keys

bat --paging=always --style=full myfile.py

This opens less, which supports vi navigation keys by default:

• j/k — scroll up/down
• g/G — jump to top/bottom
• / — search forward
• ? — search backward
• q — quit

Option 2: bat + most (more featureful pager)

BAT_PAGER="most" bat myfile.py

most supports syntax-aware scrolling and better vi-key handling.

Option 3: bat output into neovim/vim
For full vi navigation:

bat --color=always myfile.py | nvim -R -

Opens in Neovim read-only mode with full vi navigation. The --color=always passes ANSI codes which Neovim can interpret.

Option 4: delta (by the same community)
For git diff viewing specifically, delta provides syntax highlighting with navigation support. Pairs well with lazygit or git diff | delta | less.

For most use cases, bat --paging=always + less's built-in vi navigation is the simplest path. If you want fzf-style interactive file browsing with bat preview, fzf --preview 'bat --color=always {}' gives that UX.

[minanagehsalalma]

j/k are handled by the pager, not by bat itself, so the main question is whether your pipeline is actually entering a pager.

For --help output, I would try this first:

oxlint --help 2>&1 | bat --paging=always --style=plain --language=help
vitest --help 2>&1 | bat --paging=always --style=plain --language=help

A couple of details matter here:

• --paging=always makes the pager part explicit, so less gets invoked even if bat would otherwise decide not to page.
• j/k, /, g, G, and q come from less (or whichever pager is behind bat), not from bat itself.
• For CLI --help text, --language=help is usually a better fit than -l man. The man syntax is more useful for actual manpage-formatted output.

If you still see literal j/k characters after that, check PAGER / BAT_PAGER. In that case bat is probably not running through less at all.