It literally looks like a clone of fzf or sk complete with prompt and file previews. The fact that ithe article doesnβt event reference the prior art is deeply concerning.
Also if you are looking for a replacement for find that is not a full tui then take a look at fd which works more like what the author expected from the find commad - fd <pattern>.
Plus, IIRC fd does breadth-first search, which leads to faster finds in the most common cases.
Iβve been corrected. fd doesnβt do this; other find replacements exist that do, though.
I donβt think so, where did you get that? Last I checked, they werenβt interested in adding it. Thatβs why tools like bfs exist.
Oh. Iβm just straight up wrong about that; I thought Iβd read that about it back when I first started using it regularly.
Iβm just attributing it to some other tool. Bad info, sorry!
find can be a bit slow because it enumerates every directory recursively from the root you specified, but it letβs you do a lot more than just search by name. locate is available on most distros and give fast results, albiet from when the index was last rebuilt (usually nightly). They both have the vital property that they output a list of files to stdout for further processing.
Sounds fantastic, but unfortunately none of the instructions for Debian-based, or the pre-compiled binary, or the building from source worked.
So many linux posts seem to be new people getting frustrated at their lack of knowledge and trying to reinvent something that already exists. Iβm looking at this thinking, why didnβt they just use locate and fzf?
