gron
zsh-history-substring-search
Our great sponsors
gron | zsh-history-substring-search | |
---|---|---|
64 | 14 | |
13,483 | 2,433 | |
- | 1.6% | |
0.0 | 3.8 | |
6 months ago | about 2 months ago | |
Go | Shell | |
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.
gron
-
Frawk: An efficient Awk-like programming language. (2021)
gron (https://github.com/tomnomnom/gron) to transform it and query and then invert the transformation?
- Show HN: Flatito, grep for YAML and JSON files
- Gron: Make JSON greppable
-
Make JSON Greppable
It buffers all of its output statements in memory before writing to stdout:
https://github.com/tomnomnom/gron/blob/master/main.go#L204
- Ask HN: What are some unpopular technologies you wish people knew more about?
-
Jaq – A jq clone focused on correctness, speed, and simplicity
Have you tried `gron`?
It converts your nested json into a line by line format which plays better with tools like `grep`
From the project's README:
▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page..." | fgrep "commit.author"
json[0].commit.author = {};
json[0].commit.author.date = "2016-07-02T10:51:21Z";
json[0].commit.author.email = "[email protected]";
json[0].commit.author.name = "Tom Hudson";
https://github.com/tomnomnom/gron
It was suggested to me in HN comments on an article I wrote about `jq`, and I have found myself using it a lot in my day to day workflow
-
Interactive Examples for Learning Jq
> So all I want is a tool to go from json => line oriented and I will do the rest with the vast library of experience I already have at transformations on the command line.*
The tool for that is likely https://github.com/tomnomnom/gron
-
Modern Linux Tools vs. Unix Classics: Which Would I Choose?
If JQ is too much, see GRON &| Miller
gron transforms JSON into discrete assignments to make it easier to grep for what you want https://github.com/tomnomnom/gron
Miller is like awk, sed, cut, join, and sort for data formats such as CSV, TSV, JSON, JSON https://github.com/johnkerl/miller
- XML is better than YAML
-
jq 1.7 Released
And jless [1] and gron [2].
This is the first I'm hearing of gron, but adding here for completeness sake. Meanwhile, JSON seems to be becoming a standard for CLI tools. Ideal scenario would be if every CLI tool has a --json flag or something similar, so that jc is not needed anymore.
[1] https://jless.io/
[2] https://github.com/tomnomnom/gron
zsh-history-substring-search
-
Fly through your shell history
How does this differ from https://github.com/zsh-users/zsh-history-substring-search ? Except that yours seems to be built-in and zsh-history-substring-search is ~800 lines of zsh
-
Make Your Linux Terminal Enjoyable to Use
git clone --depth 1 "https://github.com/zsh-users/zsh-history-substring-search" $HOME/.oh-my-zsh/custom/plugins/zsh-history-substring-search
-
Show HN: TBMK – A Commands Bookmark for Terminal
Agreed, but also https://github.com/zsh-users/zsh-history-substring-search for me.
I can't life without this one anymore
-
What plugin is used to autocomplete paths? (Here the user types ~ and / and the path to the file is automatically shown)
It is the feature of fish shell, which is also ported to zsh via zsh-history-substring-search plugin.
-
History: how to suggest previous ls... command
zsh-history-substring-search: This is a clean-room implementation of the Fish shell's history search feature, where you can type in any part of any command from history and then press chosen keys, such as the UP and DOWN arrows, to cycle through matches.
-
zsh
In most shells, you can make use of Ctrl+R to perform backwards search through your history. After pressing Ctrl+R, you can type a substring you want to match for commands in your history. As you keep pressing it, you will cycle through the matches in your history. This can also be enabled with the UP/DOWN arrows in zsh.
-
Does anyone know the best practice insofar as where to place aliases, plugins and functions
That doesn't have the same behavior as fish. This plugin does: https://github.com/zsh-users/zsh-history-substring-search
-
Fixed the meme
zsh-history-substring-search allows you to do the same thing in zsh
-
Finding that command you need
In that case, history substring search can come in handy.
-
My favorite zsh history plugin
if you're going to use a fork of zdharma's work, this one might be better https://github.com/zsh-users/zsh-history-substring-search (maintained by a group)
What are some alternatives?
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
fzf - :cherry_blossom: A command-line fuzzy finder
jfq - JSONata on the command line
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
xidel - Command line tool to download and extract data from HTML/XML pages or JSON-APIs, using CSS, XPath 3.0, XQuery 3.0, JSONiq or pattern matching. It can also create new or transformed XML/HTML/JSON documents.
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
pup - Parsing HTML at the command line
zsh4humans - A turnkey configuration for Zsh
JsonPath - Java JsonPath implementation
zsh-syntax-highlighting - Fish shell like syntax highlighting for Zsh.
fx - Terminal JSON viewer & processor
libqalculate - Qalculate! library and CLI