When comparing tmux vs ripgrep, the Slant community recommends tmux for most people. In the question“What are the best shell powertools?” tmux is ranked 1st while ripgrep is ranked 4th. The most important reason people chose tmux is:
As long as you don't close your session, you may even lose your SSH connection, it'll keep your state just as it was. So you can resume where you left off (via `tmux attach`).
Ranked in these QuestionsQuestion Ranking
Pro Preserve the state
As long as you don't close your session, you may even lose your SSH connection, it'll keep your state just as it was. So you can resume where you left off (via
Pro Maximize screen space
As a tiling window manager, it'll make use of all the space. As you have multiple workspaces and you can resize, etc. you can adjust to see what matters most.
Pro Easily split panes
There is a keyboard shortcut that makes it easy to split a window and create more panes.
Pro Mouse support
Mouse support can optionally be enabled, allowing e.g. scrolling with the mouse wheel, or switching panes with mouse clicks.
Pro Windows linked to sessions
tmux calls the individual shell instances windows. They are displayed like tabs in the status line. These windows can be shared between different sessions, so that any given shell instance can be in any number of tmux sessions used for different purposes or by different users. This allows configurations like the following example: User A: wAB, wA1, wA2; User B: wB1, wAB, wB2
Pro Frequently updated
Tmux is in a state of constant development. Updates are frequent and bug reports usually get an answer within days.
ripgrep has performance similar to raw grep but provides similar level of usability as The Silver Searcher or ACK.
Pro Supports VCS ignore files
ripgrep can speed up by ignoring files matched by pattern in ".rgignore" (deprecated), ".ignore" (since rg-v0.2.0), and VCS ignore files (e.g., currently only ".gitignore").
Pro Speedy even with Unicode (UTF-8) searches
Pro Lock-free parallel recursive directory search
Pro ripgrep lets you only search certain types of files via file type whitelist
Con Bad scrolling support
Con No builtin telnet or serial support
It's considered bloat by the maintainers and for this reason there's no builtin support for them.
Con Does not support backreferences
Con Does not support arbitrary lookahead/lookbehind assertions
Con Does not support encodings other than UTF-8
If you need to search files with text encodings other than UTF-8 (like UTF-16), then ripgrep won’t work. ripgrep will still work on ASCII compatible encodings like latin1 or otherwise partially valid UTF-8. ripgrep may grow support for additional text encodings over time.
Con Does not support decompression
If you need to search compressed files, ripgrep doesn’t try to do any decompression before searching.