gron VS nvim-gps

gron (https://github.com/tomnomnom/gron) to transform it and query and then invert the transformation?

It buffers all of its output statements in memory before writing to stdout:

https://github.com/tomnomnom/gron/blob/master/main.go#L204

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

> 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

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

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

I've been using winbar.nvim with nvim-gps which depends on treesitter. Unfortunately it's been archived/deprecated but still works fine.

With the deprecation of nvim-gps we are left with LSP's more accurate code context parser nvim-navic or lspsaga. I however only use LSP for like 5 languages as opposed to treesitter since it's just easier to install all language parser

and nvim-navic or in this projects case it is its predecessor - nvim-gps

I currently use feline.nvim as a framework for creating my custom statusline, and before that I was using galaxyline.nvim. A feature that I would really like though is for each section of the statusline to able to dynamically resize based on the window size, and dissappear if the window gets narrow enough, based on some priority that I give them and some truncation rule. By truncation I mean that for instance a file path could get shortened by pathshorten(), the filetype indicator would only display the devicon and not the filetype name, nvim-gps would only use a depth of 1, etc... This behaviour would be defined by the user, but the framework would calculate which components to truncate in order to fit as many as possible in the priority that the user has chosen for each component.

I've added a pull request to support json https://github.com/SmiteshP/nvim-gps/pull/41