4 ms·
Using FZF to search the shell history is great until you don't find the command you were searching, you need to abort and what you typed is canceled. That's my
by IronBacon 7y ago
Using FZF to search the shell history is great until you don't find the command you were searching, you need to abort and what you typed is canceled. That's my only gripe with it.
I've tried to play with Zsh's Zle but wasn't able to find a way to abort FZF and retain the input, I suppose I need to modify FZF itself.
If there's a way to do it with Zsh I'm all ears...
- wstuartcl 7y agocan you explain what you are looking for i na little more detail?
- IronBacon 7y agoI'll try. I'm using Zsh, Ctrl-r is bound to fzf-history-widget. I start the history search with Ctrl-r using fuzzy as default, I input the command but it's not present in the history and something unrelated is selected, if I press Ctrl-g to abort the original input is erased. I've found at least a couple of feature requests (#389 #993) where it's suggested to bind a shortcut to the --print-query function. I think I've tried it in the past without success but having a fresh look at it right now, I think the blame is to the fzf-history-widget in the binary way it tries fetch an history line or reset the zle prompt...
- fluffything 7y agoIn Helm you can go back and forth as much as you want. Sometimes you end up in a dark alley, and you are just key press away from stepping back out and trying somewhere else.
- IronBacon 7y agoEmacs Helm? I'm so used to ido... ^__~