fd
fsearch
Our great sponsors
fd | fsearch | |
---|---|---|
172 | 52 | |
31,581 | 3,102 | |
- | - | |
8.8 | 6.5 | |
13 days ago | 6 days ago | |
Rust | C | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fd
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
ripgrep: A super-fast file searcher. You can install it using your system's package manager (e.g., brew install ripgrep on macOS). fd: Another blazing-fast file finder. Installation instructions can be found here: https://github.com/sharkdp/fd
-
Hyperfine: A command-line benchmarking tool
hyperfine is such a great tool that it's one of the first I reach for when doing any sort of benchmarking.
I encourage anyone who's tried hyperfine and enjoyed it to also look at sharkdp's other utilities, they're all amazing in their own right with fd[1] being the one that perhaps get the most daily use for me and has totally replaced my use of find(1).
[1]: https://github.com/sharkdp/fd
-
Z – Jump Around
You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.
I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.
¹ https://github.com/sharkdp/fd
² https://github.com/junegunn/fzf
-
Unix as IDE: Introduction (2012)
Many (most?) of them have been overhauled with success. For find there is fd[1]. There's batcat, exa (ls), ripgrep, fzf, atuin (history), delta (diff) and many more.
Most are both backwards compatible and fresh and friendly. Your hardwon muscle memory still of good use. But there's sane flags and defaults too. It's faster, more colorful (if you wish), better integration with another (e.g. exa/eza or aware of git modifications). And, in my case, often features I never knew I needed (atuin sync!, ripgrep using gitignore).
1 https://github.com/sharkdp/fd
- Tell HN: My Favorite Tools
-
Potencializando Sua Experiência no Linux: Conheça as Ferramentas em Rust para um Desenvolvimento Eficiente
Descubra mais sobre o fd em: https://github.com/sharkdp/fd
-
Making Hard Things Easy
AFAIK there is a find replacement with sane defaults: https://github.com/sharkdp/fd , a lot of people I know love it.
However, I already have this in my muscle memory:
-
🐚🦀Comandos shell reescritos em Rust
fd
-
Oils 0.17.0 – YSH Is Becoming Real
> without zsh globs I have to remember find syntax
My "solution" to this is using https://github.com/sharkdp/fd (even when in zsh and having glob support). I'm not sure if using a tool that's not present by default would be suitable for your use cases, but if you're considering alternate shells, I suspect you might be
-
Bfs 3.0: The Fastest Find Yet
Nice to see other alternatives to find. I personally use fd (https://github.com/sharkdp/fd) a lot, as I find the UX much better. There is one thing that I think could be better, around the difference between "wanting to list all files that follow a certain pattern" and "wanting to find one or a few specific files". Technically, those are the same, but an issue I'll often run into is wanting to search something in dotfiles (for example the Go tools), use the unrestricted mode, and it'll find the few files I'm looking for, alongside hundreds of files coming from some cache/backup directory somewhere. This happens even more with rg, as it'll look through the files contents.
I'm not sure if this is me not using the tool how I should, me not using Linux how I should, me using the wrong tool for this job, something missing from the tool or something else entirely. I wonder if other people have this similar "double usage issue", and I'm interested in ways to avoid it.
fsearch
-
Fsearch, a fast file search utility for Unix-like systems
Hi, author here.
Likely the most significant benefit is the more powerful query language. For example you can also search by file modification date or size and use boolean operators. https://github.com/cboxdoerfer/fsearch/wiki/Search-syntax
-
Bfs 3.0: The Fastest Find Yet
Yes, FSearch is the one I use, but it's not as great, per FSearch's dev:
> However, FSearch doesn't automatically detect changes made to the file system and update its index then. This is on the roadmap (it's called inotify support) but it'll never work as smooth as Everything on Windows, because the Linux kernel isn't particularly good at reporting filesystem changes
https://github.com/cboxdoerfer/fsearch/issues/26
Everything is comprehensive + instant + always up-to-date, that's so awesome a combo it's a pity it's Windows only
-
Copy all mp3-files from several subdirectories into a single directory
If you are new and wish a simple way to search, fsearch is a very nice tool.... https://github.com/cboxdoerfer/fsearch
- Ideas for activities for a University Linux Club
-
Trying to install Fsearch, but getting an apt-key/gpg error
You might consider grabbing the latest release at https://github.com/cboxdoerfer/fsearch/releases.
-
How and why am I seeing files that I have no access to?
One other program I've been particularly enjoying recently is fsearch : https://github.com/cboxdoerfer/fsearch
-
baloo is using 36 GB space, is that normal?
If you don't need content indexing, Fsearch is an alternative. I've been using it for over a year now and it's been working flawlessly. Results are near instant and the db is in single digit megabytes.
- Why searching on Gnome sucks and what can be done to improve it?
-
Does Linux have an equivalent of MFT on NTFS in Windows?
But AFAIK nothing seems to use this, def not fsearch, they have an open issue - https://github.com/cboxdoerfer/fsearch/issues/26
-
Name the tools you can't live without!
Still remember those days of arguing on /g/ where linux longbeards stallman fanboys tried to say how this or that tool was good search... but I dont want to just find something, I want to use it that second, and I want the entire system indexed... after getting some webms to showcase that instant feel it got the message across, though later someone appeared with some dmenu trickery being similarly fast and useful... anyway Fsearch that appeared soon after me is the real deal.
What are some alternatives?
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
ANGRYsearch - Linux file search, instant results as you type
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
fzf - :cherry_blossom: A command-line fuzzy finder
f2 - F2 is a cross-platform command-line tool for batch renaming files and directories quickly and safely. Written in Go!
exa - A modern replacement for ‘ls’.
Drill - Search files without indexing, but clever crawling
skim - Fuzzy Finder in rust!
edit-filenames - Renames or moves files using a text editor.
vim-grepper - :space_invader: Helps you win at grep.
QDirStat - QDirStat - Qt-based directory statistics (KDirStat without any KDE - from the original KDirStat author)