9 ms·
fd: A simple, fast and user-friendly alternative to 'find'
- tucnak 2y agoalias fd="rg --files | rg"
- GCUMstlyHarmls 2y agoThis isn't directly comparable, `fd` will find files with `X` in the name, but the `rg` alias will find all paths with `X` in it. Eg, λ mkdir wing && touch wing/xwing.exe wing/tie.exe λ fd wing wing/ wing/xwing.exe λ rg --files | rg wing wing/tie.exe wing/xwing.exe
- tucnak 2y agoI guess you're right. Isn't the former more useful in general? I find myself reaching for `:Rg` in Vim much more often than `:Files` or `:GFiles` courtesy of fzf.
- DaSHacka 2y agoThey're just completely different tools. The other day I was searching for a PDF I downloaded three years ago from a certain company. Simply ran `find ~/Downloads -iname '<company-name>'` and it immediately popped up. rg would not have helped me there. Even if I used something like rga, it would have taken significantly longer to parse the contents of every file in my home directory.
- deleted 2y ago[deleted]
- snide 2y agoBig sharkdp fan. Ty you for making awesome software that i use DAILY. bat, fd, hexyl, hyperfine I'm going to take this moment to remind all of you well-paid engineers that if we each spread $10 a month sponsoring talented software makers like sharkdp the Internet would be a better place. So many great little tools out there and we should try to support an ecosystem for them.
- seafoamteal 2y agobat, fd, and hyperfine are all by the same person??? That's incredible, I love all of these utilities.
- agumonkey 2y agoMan should write a tutorial on writing good utility software. Or teach even.
- seanw444 2y agoAccording to his website, he has: https://shark.fish/rustlab2019 https://shark.fish/rustlab2019
- agumonkey 2y agoah well, he pwned me i just wasn't aware of it :)
- PaulDavisThe1st 2y agoI would not call that a tutorial on how to write good utility software. It's a quite specific description of how sub(1) was written, and it contains some useful lessons, but not many that would apply to the broad class of "utility software". I think.
- jessekv 2y agoSeems like David Peter works at Astral now, as does Andrew Gallant (ripgrep). It's a dream team for rust cli tools over there.
- danso 2y agoWas just going to say, the fd,bat author reminds me of burntsushi (xsv, rg), in terms of the massive benefit they've added to the *nix command-line ecosystem.
- 2y ago
- oguz-ismail 2y ago$ touch $'a.\xFF' $ find -name $'*.\xFF' ./a.? $ ./fd -e $'\xFF' error: invalid UTF-8 was detected in one or more arguments Usage: fd [OPTIONS] [pattern] [path]... For more information, try '--help'. $ $ touch III $ LC_ALL=tr_TR.UTF-8 find -iname 'iii' $ LC_ALL=tr_TR.UTF-8 ./fd 'iii' III $ Every fucking time
- coldpie 2y agoCan you elaborate on what's going on here? Something like "fd" is assuming your filenames are UTF-8, but you're actually using some other encoding?
- oguz-ismail 2y agofd is assuming the argument to -e is valid UTF-8 while filenames can contain any byte but NUL and /
- porridgeraisin 2y ago"I cook up impractical situations and then blame my tools for it" Nobody cares that valid filenames are anything except the null byte and /. Tell me one valid usecase for a non-UTF8 filename.
- coldpie 2y agoUTF-8 is common now, but it hasn't always been. Wanting support for other encoding schemes is a valid ask (though, I think the OP was needlessly rude about it).
- porridgeraisin 2y agoIt's backwards compatible with ascii right? But yeah I suppose you would need support for all the other foreign-language encodings that came in between -- UCS-2 for example. But basically nobody does that. Glib (which drives all GTK apps' and various other apps file reading) doesn't support anything other than UTF8 filenames. At that point I'd consider the "migration" done and dusted.
- kstrauser 2y agoI use the heck out of fd daily and it’s in my standard installation on new machines. I’ve used find for years and it’s great in its own ways, but convenient ergonomics isn’t among them. I’m 100% on board with this recent-ish trend toward new replacement utilities that may or may not retain all of the flexibility of the originals but are vastly easier to use for common cases.
- agumonkey 2y agoAs much as i love new rust cli tools, `fd` ended up in the same bag as tar and ln.. I can never retain how to use it. I don't blame anybody .. I'm just witness that I always have to re-read the man from scratch to get anything done. And I'm not a gnu find lover.. with all its idiosyncracies.. somehow it registers better.
- School-Cotton 2y agoIf you’re having trouble remembering the order of arguments to ln, remember that it’s the same way around as cp. Worked for me. That is, if before there is something at /some/path but not /another/path , after running ln /some/path /another/path there will be something there (same as cp).
- agumonkey 2y agothanks, i still need to ignore the fact that the link on the right points to the left then
- mturmon 2y agoThis is what made the “ln” argument order click for me as well. Another piece of this parallel is that (with cp and mv) you can omit naming the destination file - you often just name the directory: cp /other/dir/foo.txt . The corresponding shortcut with ln is not naming the destination at all, and the symlink is created in the working directory: ln -s /other/dir/foo.txt Both of the above are my most common usage patterns, and the abbreviation of the second argument in both helps reinforce the parallel between cp, mv and ln.
- stouset 2y agoThe one that always trips me up is that `ln` is “dumb” about how it handles the first argument. If the first argument isn’t an absolute path, it must be relative to the second argument, and not to pwd. ln ./foo ./bar/baz ./bar/baz will be a symlink whose literal contents are `./foo` so it will look for foo in the same directory (bar), rather than in bar’s parent directory. This is totally backwards from how other utilities behave. Which is completely understandable if you know what it’s doing under the hood. But it is counterintuitive and surprising.
- grenran 2y agoannoyingly fd also stands for file descriptor
- travisgriggs 2y agoI’ll have to try this out. I admit that most of my uses of find looke like find . | grep what_i_am_looking_for Because I can never remember how finds arguments work. I like the integrated xargs like behavior as well. One thing I did not see in there was how fd handles symlink directory traversal? Searched the whole readme for it, and only found options to match on symlinks or not.
- xiphias2 2y agoThat's basically rg
- diziet_sma 2y agofd --help | rg link -C 10 Set -L --follow to descend into symlinked directories. The default is to not.
- bee_rider 2y agoI’m finding that I use locate more and more for this sort of thing. Of course, it produces a lot more output, because it looks at the whole system. But, it is still much faster than find because it runs on some kind of index or something, and it is easy enough to grep out the directory I’m interested in, if needed.
- gcmeplz 2y agolocate is nice, but I think that on most distros its index is only updated once/day (unless you adjust the cron job that updates it more often). Most of the times I'm trying to find something, I haven't modified it recently, but it can definitely lead you astray.
- meisel 2y agoPersonally I prefer bfs (https://github.com/tavianator/bfs https://github.com/tavianator/bfs) because it does a breadth-first search
- tavianator 2y agoSomeday I will get that functionality into fd :)
- meisel 2y agoLooking forward to it!
- actinium226 2y agoIs anyone else bothered by the fact that by default it ignores a lot of folders? I use `find` when I'm like 'I just want to know where on my system this is, wherever it might be' I know fd has options to not ignore things, but I can never remember them, so I just go back to find because I know it'll search everything.
- burntsushi 2y agoripgrep has the same default behavior. You just want `fd -u`. Or in ripgrep's case, `rg -uuu`. `fd`, I believe, got `-u` from ripgrep. And I can say that ripgrep got its `-u` from `ag`.
- jandrese 2y agoSame thing that drives me crazy with Windows built-in file search. The Windows one ignores AppData, which is where everything gets stashed these days.
- Joe_Cool 2y agoI completely dumped the windows search and only use voidtool's Everything when I am on a Windows box. It can search multiple indexed NTFS drives in miliseconds. Indexing is usually a few seconds since it works directly on the NTFS structures. (and it integrates with Total Commander)
- ajolly 2y agoYou should check out void tools search everything!
- kstrauser 2y agoThat’s a feature, and one of the reasons I prefer it. When I want to find a file in a git repo, say, there’s no need looking inside .git most of the time. Sometimes there is: if I don’t remember `fd -u`, there’s good old find there for me. But that’s almost never what I want to do, so fd’s defaults are sensible for me.
- 2y ago
- sandos 2y agoYeah, I was trying the -exec functionality of find just yesterday, something which Iv'e done many times before, but that was long ago. I eventually gave up! Thats how ergonomic find is :)
- rednafi 2y agoOne reason I haven’t picked up any of these newfangled Rust tools like bat, exa, or fd is that I can barely remember the options for the originals. For me, anything that isn’t a drop-in replacement for the OG tools isn’t worth the friction. I use ripgrep inside VS Code but vanilla grep on the command line because of years of muscle memory. That said, I don’t care what language a tool is written in as long as it works. One of my favorite Unix tools is GNU Stow, and it’s written in Perl. Even if these Rust tools were drop-in replacements, I probably wouldn’t bother installing them manually. As a user, the speed improvements and memory safety don’t really matter to me. There are other languages, like Go, where memory safety is guaranteed as well, and Go’s performance is more than adequate for tooling—with the added benefit of getting more engagement from the community. So I’m not entirely convinced by this “Rust is the savior” narrative. That said, if macOS or Ubuntu decided to hot-swap the OG tools with Rust alternatives that behave exactly like their predecessors, I probably wouldn’t complain—as long as it doesn’t disrupt my workflow.
- johnisgood 2y ago> One of my favorite Unix tools is GNU Stow What about https://zolk3ri.name/cgit/zpkg/ https://zolk3ri.name/cgit/zpkg/? A lot of improvements have been done behind the scenes apparently (rollback, proper states, atomicity, etc.), but I am not sure when he is willing to publish. I personally use it as-is when I am compiling stuff myself and the ZPG_DST is ~/.local/. It works well for keeping track of programs that I compile and build myself.
- whompyjaw 2y agoIt absolutely does not matter what language this tool is written in. That goes for any tool. If it’s better, use it. In this case, fd is far superior to “find” in almost every way. Sane defaults, wayyy faster, easy options (just use cht.sh if you can’t remember) To me, there is no reason to ever use “find”. If I’m on a new system, I just install fd and carry on.
- syklemil 2y ago> It absolutely does not matter what language this tool is written in. That goes for any tool. Eh, there are a lot of tools where it actually does kind of matter. I suspect for a lot of invocations of tools like `fd` and `rg`, they'll be done before an equivalent written in java has even had its JVM spin fully up. There's _tons_ of Java software, but it somehow never managed to make a dent in the CLI space. > To me, there is no reason to ever use “find”. If I’m on a new system, I just install fd and carry on. I guess I should finally have a look at how to replace my `find $path -name "*.$ext" -exec nvim {} +` habit … turns out it's `fd -e $ext -X "nvim" "" $path`
- Babkock 2y agoOne of those essential tools, that's not ever included with GNU/Linux by default, but I always install almost immediately along with ripgrep, bat, fzf, htop.
- meonkeys 2y agoAgreed! Curious what your base OS is. Mine has been Ubuntu LTS for years, but now I find myself installing so many custom tools like these I'm thinking I might want to move to NixOS or Gentoo or something like that instead. I just don't want to lose out on stability and great hardware support.
- lillecarl 2y agoHey! I would recommend trying home-manager, or just plain nix profiles before going all-in on NixOS, it's very easy to add Nix on top of any Linux (and MacOS to an extent). This way you still have your tried and true base system and you can manage things somewhat like you're used to (and use venv and whatever bullshit package manager everyone invents), a lot of common tools will work poorly on NixOS (venv, npm...)and while they have Nix alternatives that are "better" it's DIFFERENT. I run NixOS on desktop and laptop but I wouldn't recommend starting with it, you can benefit from all packages on any distro by just installing Nix. Also home-manager adoption can be incremental. ADHD end note: home-manager is perfect for CLI tools installation and config. You must unconfigure "secure path" in sudo though otherwise your CLI tools don't work with sudo
- thibran 2y agoI would add 'ouch' to the list. It allows easy compression/de-compression.
- drcongo 2y agoAnd procs - https://github.com/dalance/procs https://github.com/dalance/procs
- creeble 2y agoFor the sake of Ubuntu users, it’s ‘apt install fd-find’. You’ll need an alias fd=fdfind too.
- HeadlessChild 2y agoThis saved me a ton of time when I had to migrate id ownership of files in ancient NFS shares. [0] https://news.ycombinator.com/item?id=31489004 https://news.ycombinator.com/item?id=31489004
- alkh 2y agoImo, everyone should check https://terminaltrove.com/ https://terminaltrove.com/ from time to time. There, I have found easy replacements to commonly used tools: find -> fd, time(for runtime comparison) -> hyperfine, grep->ripgrep, asciinema + converting to .gif -> t-rec[1], manually creating convertional commits -> koji[2], etc. [1]https://terminaltrove.com/t-rec/ https://terminaltrove.com/t-rec/ [2]https://terminaltrove.com/koji/ https://terminaltrove.com/koji/
- johnisgood 2y agokoji would be fine, but I want to stick to 67 column width and I could not do it with this, I think? I use git-cola, instead.
- alkh 2y agoyeah, that's a problem for me as well. I end up doing koji->gitlint->git commit --amend --edit if there are any width issues
- imoreno 2y agoInstead of koji, I use `aider --commit`
- tmtvl 2y agoWould be nice if you could filter based on license. I really want to avoid non-(A)GPL tools where possible.
- enricozb 2y agoI wish fd and rg would align some of their flags. For example, both fd and rg have a --type, but for fd it means file/directory/symlink etc. For rg it means the file MIME type. Another example is that fd has an --extension flag, and rg doesn't. Since I believe the correlation of usage of these tools is high, I think they could benefit from having similarly named flags.
- hnlmorg 2y agoTo be honest, this is one of the reasons I usually stick with POSIX tools, I’m too old and too lazy to want to learn a whole new set of flags for a whole new set of tools that are very close to but not quite the same as what’s already part of my muscle memory now. Not taking anything away from the tools that have been written. Just for me, the pain of learning a new tool is greater than the convenience I’d gain from using it.
- renewiltord 2y agoIt's actually because they stayed compatible that the problem arises: fd and find -type mean the same but this user wants them to be different. Overall, I use AI shell completion so it's much smoother.
- hnlmorg 2y agoI’ve been thinking of adding AI completion into my CLI tools but not really sure how to implement it in a non-intrusive way. So I’ve got a few questions, if you don’t mind sharing: What’s the workflow like for AI shell completion? How does it know which flag to complete for you? Do you write a description in native language (eg English) and it completes the entire command line? Or is it more one flag at a time?
- renewiltord 2y agoAh I do it from the other side Got it from here https://x.com/arjie/status/1575201117595926530?s=46 https://x.com/arjie/status/1575201117595926530?s=46
- deleted 2y ago[deleted]
- puffybuf 2y agofzf, ripgrep are some command line tools I like. Check them out. Being able to quickly search your history with fuzzy finder is so useful.
- usrbinbash 2y agoThere are many completely unnecessary "reworks" of classic UNIX stdutils that add very little to no value, and instead pitch themselves purely on "written in {lang-the-dev-likes}" or being "blazing fast" or something similar. `fd` isn't one of those. `fd` is amazing. It is simpler, faster and easier to grok than `find`, the commands syntax is a straight up improvement, it comes with sane defaults which makes the easy things and common usecases simple, while the harder ones are way more accessible. It uses colored output in an actually useful way, its manpage is more structured and easier to read... and MOST IMPORTANTLY ...it is capable of running commands on search results with parallel execution out of the box, so no need to get GNU parallel into the command. THIS is the kind of renewal of classic command line utilitis we need! Literally the only pain point for me, is that it doesn't use glob-patterns by default, and that is easily fixed by a handy alias gf="fd -g"
- beej71 2y agoThis is an honest question, not a criticism, but how much does parallelism help? Isn't the disk a choke point?
- kstrauser 2y agoDepends greatly on the use case. If you're finding all the gifs in a directory and converting them to pngs, it may be the case that CPU is hammered harder than IO. There are surely counterexamples, too. It's a nice option to have when you need it.
- swiftcoder 2y agoA lot of developer machines are running expensive NVME SSDs, which perform well enough the disk isn't so much of a choke point. If you run on spinning rust, YMMV
- usrbinbash 2y agoTheoretically yes, practically not really (any more). NVMe cards are fast enough that a single core traversing the file system can actually be a chokepoint, so parallelisation helps a lot here. I also should have made it clear that my comment also wasn't so much about the search (although the parallel search is absolutely a nice-to-have)...it was about the `-x, --exec` being automatically in parallel. A common usecase is to find all files of X criteria, and then perform the same operation on all of them, e.g. find all session logs older than N days and then compress them, or convert all wav files in a directory tree to mp3 If the operation is computationally expensive, using more than one core speeds things up considerably. With `find`, the way to do that was by piping the output to GNU parallel. With `fd` I can just use `-x, --exec` and it automatically spins up threads to handle the operations, unless instructed not to.
- pimlottc 2y agoFor folks on macOS, you can also use "mdfind" as a command-line interface for macOS Spotlight search https://ss64.com/mac/mdfind.html https://ss64.com/mac/mdfind.html
- kstrauser 2y agoI never remember what it's called, so I have `alias locate 'mdfind -name'` in my shell setup.
- pimlottc 2y agoIf it helps you remember, it appears that the "md" in "mdfind" stands for "metadata" [0] 0: https://en.wikipedia.org/wiki/Spotlight_(Apple)#macOS https://en.wikipedia.org/wiki/Spotlight_(Apple)#macOS
- kstrauser 2y agoYeah, for some reason my brain's incapable of pinning that in cache. Oh well, that's what they invented aliases for in the first place.
- spudlyo 2y agoConsidering how many as many CPU cycles and iops that Spotlight robs from you on a regular basis, you might as well get some use out of it.
- BeetleB 2y agoI never managed to use find. I would always find a different way to solve my problem (e.g. Midnight Commander). I use fd all the time. Simply having a better command line interface is a big deal.
- ilyagr 2y agoI got used to https://github.com/tavianator/bfs https://github.com/tavianator/bfs instead. Breath-first ordering is nice. Interestingly, the author is listed as one of the maintainers of `fd` as well.
- singhrac 2y agoI use fd all the time. I admit it, I couldn't get the muscle memory right for find. One day I'll be on a bare Linux installation where I can't cargo install whatever I want and I'll have to ask ChatGPT to generate my find commands. I like `fd -o {user}` and `fd --newer {time}` to find recently changed files and owned by others.
- derefr 2y agoI was just thinking yesterday that I'd appreciate a more modern alternative to find(1). Not a simplified one, though! The original problem that led me to thinking about this, was that I wanted to do a search that would include all files below the current directory, except if they were within a specific subdirectory. (Why not just `grep -v` for that directory? Because the subdir contained millions of files — in part, I was trying to avoid the time it would take find(1) just to do all the system calls required to list the directory!) And yes, this is possible to specify in find(1). But no, it's not ergonomic: find . -path ./excluded_dir -prune -o -type f -print You can add parentheses, if you like. (But you don't have to. It seems find(1) has implicit Pratt parsing going on): find . \( -path ./excluded_dir -prune \) -o \( -type f -print \) This incantation entirely changed my perspective on find(1) as a tool. Until I learned this, I had never understood exactly why find(1) nags you to put its arguments in a specific order. But this makes "what find(1) does under the covers" very clear: it's assembling your expression into a little program that it executes in the context of each dirent it encounters on its depth-first traversal. This program has filtering instructions, like `-path`, and side-effect instructions, like `-print`. You can chain as many of each as you like, and nest them arbitrarily within (implicit or explicit) logical operators. After some further experimentation, I learned that find's programs are expression-based; that every expression implicitly evaluates to either true or false; and that any false return-value anywhere in a sub-expression, is short-circuiting for the rest of that sub-expression. (You could think of every instruction as being chained together with an implicit &&.) This means that this won't print anything: find . -false -print In other words, my original expression above: find . -path ./excluded_dir -prune -o -type f -print ...is actually this, when translated to a C-like syntax: (path("./excluded_dir") && prune()) || (type("f") && print()) As soon as I realized this, I suddenly became very annoyed with find(1)'s actual syntax. Why is find(1) demanding that I write in this weird syntax with leading dashes, various backslash-escaped brackets, etc? Why can't I "script" find(1) on the command-line, the same way I'd "script" Ruby or Perl on the command-line? Or heck, given that this whole thing is an expression — why not Lisp? find '(or (and (path "./excluded_dir") prune) (and (type f) print))' I do understand why find(1) was designed the way it was — it's to allow for shell variable interpolation, and to rely on shell argument tokenization. But it's pretty easy to work around this need — just push both of these concerns "to the edge" (i.e. outside the expression itself. Like SQL statement binding!) • Support $VAR syntax for plain references to exported env-vars. • Support positional binding syntax (?1 ?2 ?3) for positional arguments passed after the script. • Support named binding syntax (?foo) for positional arguments after the script that match the pattern of a variable-assignment (ala make(1) arguments): find '(or (and (path ?excluded_dir) prune) (and (type f) (iname ?1) print))' foo excluded_dir="${bar[1]}" I don't know about you, but I personally find this grammar 10x easier to remember than what find(1) itself has going on.
- linza 2y agoI find these tools super awesome, but i never use them beyond trying them out once, because they don't usually come with coreutils or something like that. Haven't found a way to use these tools in a user-local way. For my own homemade tools, i put the binary in my dotfiles and they end up in .local/bin and i can use them by default. I can do that because I don't need to update them.
- theflyinghorse 2y agoAfter using nushell for a few month it's really hard for me to go back to the old ways. A million of different tools all with different API and outputs are just not the way to go
- greggh 2y agoEvery new install gets zsh, kitty, exa, fzf, bat, ripgrep, fd, neovim, ducker, qman, cht.sh, navi, and hyperfine as the first things I do.
- metaltyphoon 2y agozsh, fzf, bat, rg, fd, neovim, tldr, lazygit, jq, yazi, starship, hyperfine, ghostty.
- helsinki 2y agoNow we're talking.
- Tomte 2y ago> fd is distributed under the terms of both the MIT License and the Apache License 2.0. So not dual-licensed (MIT OR Apache-2.0), but MIT AND Apache-2.0? That's unusual. Later: it seems they intended dual-licensing, and botched the wording: https://github.com/sharkdp/fd/issues/105 https://github.com/sharkdp/fd/issues/105
- coldtea 2y agoAmazing program. Along with rg great QOL improvements
- terminaltrove 2y agoif you want to try fd, bat, numbat, hexyl and hyperfine, you can install them quickly and see screenshots of them below on Terminal Trove: fd - https://terminaltrove.com/fd/ https://terminaltrove.com/fd/ bat - https://terminaltrove.com/bat/ https://terminaltrove.com/bat/ numbat - https://terminaltrove.com/numbat/ https://terminaltrove.com/numbat/ hyperfine - https://terminaltrove.com/hyperfine/ https://terminaltrove.com/hyperfine/ hexyl - https://terminaltrove.com/hexyl/ https://terminaltrove.com/hexyl/ we make a real effort to ensure that you can install them with the ability to see the screenshots.
- jwrallie 2y agoNice suggestions, I’ll be definitely trying numbat and hyperfine (I already use fd daily). I could see bat being useful only as the last program on a long pipe chain, but I really like xxd so I will pass on hexyl.
- andy_xor_andrew 2y agocool site, have you considered using asciicinema instead of screenshots? Seems like the perfect tool for what you're trying to do https://asciinema.org/ https://asciinema.org/
- archon810 2y agoI clicked on several utils on the site, and they all had GIFs of the demos. I think terminaltrove takes these from the projects themselves instead of creating them on their own.
- d0mine 2y agoPerhaps something like https://github.com/xtermjs/xterm.js https://github.com/xtermjs/xterm.js can be used to show interactive sessions for TUI apps.
- nchmy 2y agoI look forward to exploring the tools some more. Though, I install everything these days via mise (which you list as well). Would be cool if you had mise commands - be it just mise use -g fd or for other tools that arent in their registry, how to use the backends like mise use -g cargo:xyztool
- mrobot 2y agoHas anyone made an awk replacement? I find awk get's really annoying and ugly really fast, as things become even mildly complicated. I feel like awk could be so much better.
- TylerE 2y agoFor me anything beyond the most trivial one liner I just write in python or whatever. Maintainability >>>>>>> terseness. It's not 1976 where every cycle matters.
- zie 2y agoI honestly never use find anymore, I just use ripgrep(rg). rg is so fast, that I don't worry about the ridiculously extra overhead of searching content. I can't remember the last time I used find.
- luckman212 2y agoI just released an Alfred workflow[0] for searching a group of user-defined directories, that heavily relies on fd under the hood. Thank you @sharkdp for this amazing tool, I use it every day and it is wonderful. Hyperfine is another underrated gem that is just so great. [0] https://github.com/luckman212/alfred-pathfind/ https://github.com/luckman212/alfred-pathfind/
- foresto 2y agofd is also a file & directory maintenance command by Shirai Takashi. (Package name: fdclone) I think it has been around for at least couple of decades.
- keithnz 2y agoOn windows, for those that don't know, use Everything from https://www.voidtools.com/ https://www.voidtools.com/ This is a VERY fast file searching tool. It's crazy good.
- nout 2y agoMy favorite way is to just have this in my zsh aliases. # Find file by prefix (ignore case). # Usage: 'f' or 'f myfile' or 'f myfile.txt \etc' # or f '*css' function f() { find ${2:-.} -iname "${1}*" 2>/dev/null | grep '^\|[^/]*$' } # We use noglob, so zsh doesn't expand characters like "*" # and so we can do e.g. f *css alias f='noglob f'
- anacrolix 2y agoI like it but the defaults are super annoying. I'm always trying to find things I can't otherwise but it defaults to ignoring git dirs and dot files, literally the thing I search for the most
- DrNosferatu 2y agoNo flatpak / snap for latest version and automated upgrades?
- chinabot 2y agoWorks really well for me. tks
- kiitos 2y agoCOMMAND OUTPUT WALLCLOCK_SEC USR_SEC SYS_SEC time find ~ -iregex '.*\.jpg$' | wc -l 14372 45.04 4.59 13.23 time find ~ -iregex '.*\.jpg$' | wc -l 14372 48.42 4.60 13.59 time find ~ -iname '*.jpg' | wc -l 14372 44.55 1.07 13.57 time find ~ -iname '*.jpg' | wc -l 14372 44.94 1.08 13.64 time fd '.*\.jpg$' ~ | wc -l 14325 4.01 2.67 24.16 time fd '.*\.jpg$' ~ | wc -l 14325 4.37 2.73 30.28 time fd -g '*.jpg' ~ | wc -l 14325 3.98 2.72 25.84 time fd -g '*.jpg' ~ | wc -l 14325 4.04 2.69 26.82 Good to use concurrency, predictable impact on all of the various timings. Different results vs. find for the same term (assumedly) are unexpected? Did I mess up the translations?