fzf-fish-integration VS sublime-fish

Fyi; I assume you already checked out fzf.fish ?

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

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.

It doesn't. Not really. It has an awkward set of words and regexes that it uses to highlight fish. A while back they reused the bash definitions, it seems now they've switched to sublime's fish syntax. The TODOs there should tell you some of the limitations.