grex
fzf
Our great sponsors
grex | fzf | |
---|---|---|
27 | 407 | |
6,521 | 59,739 | |
- | - | |
8.7 | 9.6 | |
8 days ago | about 23 hours ago | |
Rust | Go | |
Apache License 2.0 | MIT License |
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.
grex
- grex 1.0.0 - Generate regular expressions from user-provided test cases
- Generating regex pattern automatically
-
Regex generator
Sounds like you're looking for something like grex. Mind you, this does not save you from learning about regular expressions. It‘s more of a supporting tool.
- When you have a problem and solve it using RegEx, you end up with two problems
-
Gnarly Learnings from August 2022
grex-js
- Grex – Generate regular expressions from test cases
-
grex 1.4.0 - Generate regular expressions from user-provided test cases
Command-line tool and Rust library: https://github.com/pemistahl/grex
- Regex finder
-
RegExr: Learn, Build and Test Regex
If I understood what you mean, then yes, I bout one https://regex.help/ (powered by https://github.com/pemistahl/grex doing the heavy lifting).
- grex is a library as well as a command-line utility that is meant to simplify the often complicated and tedious task of creating regular expressions. It does so by automatically generating a single regular expression from user-provided test cases.
fzf
-
Ask HN: Any tool for managing large and variable command lines?
In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.
Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399
-
pyfzf : Python Fuzzy Finder
fzf : https://github.com/junegunn/fzf
- Command Line Fuzzy Search
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Those are the most used aliases in my gitconfig.
"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf
"git gone" removes local branches that don't exist on the remote.
"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide
-
Which command did you run 1731 days ago?
> my history is so noisy I had to find another way
The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].
[1]: https://github.com/junegunn/fzf#search-syntax
[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...
-
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
-
alacritty-themes not working any more!!!
View on GitHub
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues
[1] https://github.com/junegunn/fzf
[2] https://github.com/PatrickF1/fzf.fish
-
Ugrep – a more powerful, ultra fast, user-friendly, compatible grep
You can also use fzf with ripgrep to great effect:
[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...
- Tell HN: My Favorite Tools
What are some alternatives?
yaegi - Yaegi is Another Elegant Go Interpreter
peco - Simplistic interactive filtering tool
rust-csv - A CSV parser for Rust, with Serde support.
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
pomsky - A new, portable, regular expression language
z - z - jump around
codetour - VS Code extension that allows you to record and play back guided tours of codebases, directly within the editor.
zsh-autosuggestions - Fish-like autosuggestions for zsh
parallel-disk-usage - Highly parallelized, blazing fast directory tree analyzer
mcfly - Fly through your shell history. Great Scott!
percol - adds flavor of interactive filtering to the traditional pipe concept of UNIX shell
ranger - A VIM-inspired filemanager for the console