jp
fzf
Our great sponsors
jp | fzf | |
---|---|---|
6 | 407 | |
716 | 59,739 | |
1.8% | - | |
1.1 | 9.6 | |
11 months ago | 4 days ago | |
Python | 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.
jp
-
Jq Internals: Backtracking
I have a hard time suggesting such a thing, because I find JMESPath incredibly inferior to jq's expressiveness, but if you're in the AWS ecosystem much, you may enjoy https://github.com/jmespath/jp#readme which uses the same query language as does awscli (https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-f...). That may at least pay more dividends than keeping jq's language in your head where it will only ever be used by jq
-
using JQ to parse output
Have you tried this utility instead: https://github.com/jmespath/jp
- Zq: An Easier (and Faster) Alternative to Jq
- What tools did you discover that made your work so much easier for DevOps & SRE
-
FX: An interactive alternative to jq to process JSON
There’s also jp, which interprets JMESPath: https://github.com/jmespath/jp
This one has the advantage of being natively understood by aws-cli, meaning you can pass a JMESPath to an AWS call and only receive the filtered / transformed result back.
- Tips on Adding JSON Output to Your CLI App
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?
jq - Command-line JSON processor
peco - Simplistic interactive filtering tool
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
fx - Terminal JSON viewer & processor
z - z - jump around
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
zsh-autosuggestions - Fish-like autosuggestions for zsh
scout - Reading and writing in JSON, Plist, YAML and XML data made simple when the data format is not known at build time. Swift library and command-line tool.
mcfly - Fly through your shell history. Great Scott!
jid - json incremental digger
ranger - A VIM-inspired filemanager for the console