dotfiles VS fzf-fish-integration

I've used Fish for a while ([my dotfiles tell me I've been using it for 8 years now... how the time flies!](https://github.com/LukeChannings/dotfiles/blob/148a5021da464...)) and decided to give Nu a try.

The main problem with Nu is that it can't really be used as a full-time shell because it doesn't support job control, so a lot of nodejs-based CLIs I need for my job seem to lock up the shell. I got around it by using pueue (a daemon that manages processes), but it's clunky to say the least.

I do think it'll get better as it matures, but I've been through all that pain with Fish and I'm not sure I want to put myself through that again.

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