procs VS fzf-fish-integration

You can have a look at this repo for some inspiration, since it's mostly cross platform. It uses the winapi crate for Windows and the procfs for Unix.

procs is a ps replacement. It provides colorized human-readable output, multi-column search, more information than ps, docker support, paging, watch mode, and tree view. It is a much more user-friendly and modern alternative to ps. You can filter by name and PID and use logical and/or operators to combine multiple filters. It also has a tree view which is very useful for seeing the process hierarchy. It can also show docker container names for the process running docker containers.

ps replacement - Procs

prox: A modern replacement for ps written in Rust.

For example, add the below entry to the TOML config file if you want to download the procs tool as well.

Preview process trees (using procs)

I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues

[1] https://github.com/junegunn/fzf

[2] https://github.com/PatrickF1/fzf.fish

I like https://github.com/PatrickF1/fzf.fish

Can also do cool stuff like search for a file to open in $EDITOR and searching git log

There is new pull request with new function for fzf.fish, that enables fzf-tab completion.

It may be worth checking the fzf plugin you're using with Fish. There is a more recent+maintained effort[0] that brings an even more delightful feature set, particularly with Ctrl+R/_fzf_search_history

[0] https://github.com/PatrickF1/fzf.fish/wiki/Prior-Art

I missed the shell integration when switching to Fish a couple of years ago. fzf.fish saved the day, I wouldn't be without the keybindings now (Ctrl+Alt+F is roughly the equivalent of `*`)

https://github.com/PatrickF1/fzf.fish

source: fzf.fish

I am the creator of fzf.fish plugin. I'm currently looking for ways to improve the plugin, especially for ideas to simplify it and make it more accessible for everyone, not just power users.

Shameless plug for https://github.com/PatrickF1/fzf.fish, which definitely covers searching your history and has plenty of other usages the commandline command, mentioned above.

For commands with many arguments that are in the history, history search is absolutely better than auto-suggest, yes. But I'd also recommend fzf + fzf.fish in that case, for turbo-charged history (and other) searches.

I put a some time and effort in it, but i've been greatly influenced by the excellent PatrickF1/fzf.fish: Augment your fish command line with fzf key bindings. (github.com) plugin, with its great configuration management (using a dedicated function).