skim

Well there's been skim (https://github.com/skim-rs/skim) for a while as a fzf equivalent in Rust.

> I’m also not sure the ‘fuzzy’ aspects of Atuin quite match the heights of fzf/skim). This. I've been using atuin for a few months and this is so horrible how much better it could be with a "real" fzf matching... I just tried skim shell integration ( https://github.com/skim-rs/skim/tree/master/shell ) and it's great. I kind of like the extra metadata atuin saves (cwd, session context), but I think I was just waiting to stumble into this to turn atuin back off...

I tried to switch to Skim https://github.com/lotabout/skim since it's meant to be "fzf but in rust" but it wasn't quite there yet. fzf is incredible.

I love fuzzy shell history. Game changer in terms of shell productivity. I use atuin[0] instead of fzf as I find the experience a bit nicer and it has history backups built in (disclaimer, I am a maintainer) Some of our users still prefer fzf because they are used to how it fuzzy finds, but we're running an experiment with skim[1] which allows us to embed the fuzzy engine without much overhead - hopefully giving them back that fzf-like experience [0]: https://github.com/ellie/atuin [1]: https://github.com/lotabout/skim

You state that as a blank and white fact, but there's nuance. https://github.com/lotabout/skim/issues/317#issuecomment-652...

I use skim / `sk` for this kind of task: https://github.com/lotabout/skim . For example, for iterating on jq incantations, I have in my shell rc file: function jqsk { sk --tac --ansi --regex --query . --multi --interactive --cmd '{}' \ --bind 'enter:select-all+accept,ctrl-y:select-all+execute-silent(for line in {+}; do echo $line; done | pbcopy)+deselect-all' \ --cmd-history=${HOME}/.sk_history --cmd-history-size=100000 \ --no-clear-if-empty \ --cmd-query "cat $1 | jq --raw-output --color-output --exit-status '.'" } I should look into whether fzf or any of the other tools in this thread can be coerced into doing the same thing, the above is pretty verbose and arcane, and it doesn't always behave the way I expect.

That's a good question. I'd be interested in any benchmark you saw. And although it seems like sk has come a long way since 2020[0], it may still be slower reading in a larger file. I really don't know. But I suppose I'd ask -- faster how? The linked benchmark really doesn't mean much to me. As an interactive app I judged it on how it felt latency-wise at the CLI. So, I would just try to scroll page-up while find was feeding in the files in my home directory. fzf would sometimes stall on my system (again not scientific) and would occasionally junk up the terminal when it got fed something strange. This could be a problem with fzf or it could have been a problem with how I was using it. On the other hand, sk at the CLI has been rock solid and very fast. skim as a library needs better docs and has a few other teething issues, but I'm

I have been really inspired by 'fzf' recently. Wrote a fun little ZFS utility[0] which I intended to just script with 'fzf', but have since found skim[1], or 'sk', and now use it both as my sole fuzzy finder app (because it's supposed to be interactive and it's faster!), and as a library for my little utility. I like them both for making fun zsh key bindings, so, so easy. [0]: https://github.com/kimono-koans/httm [1]: https://github.com/lotabout/skim

I do the same thing (want to iterate on some complicated jq query -- or, let's be real, blunder around with my loose grasp of jq). I use https://github.com/lotabout/skim#interactive-mode instead of fzf. function jqsk { sk --tac --ansi --regex --query . --multi --interactive --cmd '{}' \ --bind 'enter:select-all+accept,ctrl-y:select-all+execute-silent(for line in {+}; do echo $line; done | pbcopy)+deselect-all' \ --cmd-history=${HOME}/.sk_history --cmd-history-size=100000 \ --no-clear-if-empty \ --cmd-query "cat $1 | jq --raw-output --color-output --exit-status '.'" } I run it like `jqsk file.json` and then change the `'.'` in the cmd-query to whatever I'm trying to do with jq. I'll definitely look into some of the other mentioned solutions for this though. I settled on skim a year+ ago and haven't r

If you like fzf, give skim [1] a go. It's basically faster (anecdotally) fzf, but can also be used as a Rust library. I made a little personal to-do manager using it, together with SQLite for persistence. I also improved my fish shell ergonomics with [2]. [1] https://github.com/lotabout/skim [2] https://github.com/zenofile/fish-skim

If anyone is interested in a rust version (probably the main benefit being you can use it as a rust library) there is a similar tool called skim[1] It's actively developed and seems to have a non-overlapping set of features with fzf other than the basics (they both have features the other doesn't, and skim copies most of the core ui from fzf) [1] https://github.com/lotabout/skim

There's also skim[1], which would be a Rust fzy alternative. But neither fzy nor skim quite do what fzf does, which is offer an simple feature-filled experience out of the box. The big draw is fzf Just Works™. I don't mind that it feels bloated and slow sometimes, because I don't want to spend a week figuring out how to make the other two do what fzf does without configuration or drama, and all the speed improvements in the world doesn't really matter when the bottleneck is the meatball behind the keyboard. [1]https://github.com/lotabout/skim

The integration with fzf seems nice. Any plans to integrate with skim, a Rust implementation of fzf? https://github.com/lotabout/skim