the_silver_searcher
fd
the_silver_searcher | fd | |
---|---|---|
59 | 172 | |
25,720 | 31,581 | |
- | - | |
0.0 | 8.8 | |
4 months ago | 17 days ago | |
C | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
the_silver_searcher
-
Essential Command Line Tools for Developers
View on GitHub
-
Debugging Silent Create Action Failures in Rails
If you have trouble finding it among the other stuff happening in the server log, well, so do I! I recommend learning how to programmatically search through your terminal output. Providing a universal method for this is challenging because various tools and terminal emulators implement this functionality differently. Another option would be to use tools like grep or the_silver_searcher (a favorite of mine) to search the file where your dev logs are written to. This file is located at log/development.log in a Rails project.
- Ggreer/the_silver_searcher: A code-searching tool similar to ack, but faster
-
✨7 Github Repositories to Master React
Some of the examples below use ag, but could just as well use grep or equivalent.
-
Rust crate rg typosquatting/redirect to ripgrep
Why guess when [there are installation instructions for various platforms on the README](https://github.com/ggreer/the_silver_searcher#installing)?
Also, although it may not be easy to remember, is this really a problem in practice given the installation count in most contexts is one? If there's a context where it's installed regularly, that's a one-time addition to an install script, Dockerfile, etc. in my experience. Do you have a situation that isn't amenable to that?
-
Linux drivers development
The kernel changes a lot, so the books would get outdated quickly. But you can find simple / similar drivers, and read the code. Usually there are some documentation / comments on the headers before the function declarations. The Elixir and the Silver Searcher will help a lot.
-
🚀 Boost Your Coding Productivity with These 9 Powerful FREE Tools! 💪
URL 🔗 : https://github.com/ggreer/the_silver_searcher
-
how to list places where a function is being used?
My "vim" way of finding all the places where a function is being used: using visual mode, marking the function, and passing it to :Ag (silversearcher) The problem with this is that it is not 100% accurate, since it will just look for things with the same name, so I was thinking about using the LSP to make things more robust.
-
Any Linux admins willing to try Pygrep?
We're fans of ag, The Silver Searcher.
-
How do I tell helm-ag to ignore files with a particular file extension?
Helm-ag is an interface to the ag, silver-searcher, so check the docs for ag. For example, ag automatically ignore some files if there is a .gitignore with some file patterns, or you could use .agignore.
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.
What are some alternatives?
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
Visual Studio Code - Visual Studio Code
intellij-plugins - Open-source plugins included in the distribution of IntelliJ IDEA Ultimate and other IDEs based on the IntelliJ Platform
fzf - :cherry_blossom: A command-line fuzzy finder
exa - A modern replacement for ‘ls’.
opengrok - OpenGrok is a fast and usable source code search and cross reference engine, written in Java
skim - Fuzzy Finder in rust!
ack3 - ack is a grep-like search tool optimized for source code.
vim-grepper - :space_invader: Helps you win at grep.