.png)
1 hour ago
2
a TUI playground for exploring jq.
This application utilizes itchyny's implementation of jq written in Go, gojq.
Available through the Arch User Repository as jqp-bin.
Download the relevant asset for your operating system from the latest GitHub release. Unpack it, then move the binary to somewhere accessible in your PATH, e.g. mv ./jqp /usr/local/bin.
Clone this repository, build from source with cd jqp && go build, then move the binary to somewhere accessible in your PATH, e.g. mv ./jqp /usr/local/bin.
jqp also supports input from STDIN. STDIN takes precedence over the command-line flag. Additionally, you can pass an optional query argument to jqp that it will execute upon loading.
| tab | cycle through sections |
| shift-tab | cycle through sections in reverse |
| ctrl-y | copy query to system clipboard1 |
| ctrl-s | save output to file (copy to clipboard if file not specified) |
| ctrl-c | quit program / kill long-running query |
| enter | execute query |
| ↑/↓ | cycle through query history |
| ctrl-a | go to beginning of line |
| ctrl-e | go to end of line |
| ←/ctrl-b | move cursor one character to left |
| →/ctrl-f | move cursor one character to right |
| ctrl-k | delete text after cursor line |
| ctrl-u | delete text before cursor |
| ctrl-w | delete word to left |
| ctrl-d | delete character under cursor |
| ↑/k | up |
| ↓/j | down |
| ctrl-u | page up |
| ctrl-d | page down |
jqp can be configured with a configuration file. By default, jqp will search your home directory for a YAML file named .jqp.yaml. A path to a YAML configuration file can also be provided to the --config command-line flag.
If a configuration option is present in both the configuration file and the command-line, the command-line option takes precedence. For example, if a theme is specified in the configuration file and via -t/--theme flag, the command-line flag will take precedence.
Themes can be specified on the command-line via the -t/--theme <themeName> flag. You can also set a theme in your configuration file.
Overrides to the chroma styles used for a theme can be configured in your configuration file.
For the list of short keys, see chroma.StandardTypes. To see which token to use for a value, see the JSON lexer (look for <token> tags). To see the color and what's used in the style you're using, look for your style in the chroma styles directory.
You can change non-syntax colors using the styleOverrides key:
Themes are broken up into light and dark themes. Light themes work best in terminals with a light background and dark themes work best in a terminal with a dark background. If no theme is specified or a non-existent theme is provided, the default theme is used, which was created to work with both terminals with a light and dark background.
- abap
- algol
- arduino
- autumn
- borland
- catppuccin-latte
- colorful
- emacs
- friendly
- github
- gruvbox-light
- hrdark
- igor
- lovelace
- manni
- monokai-light
- murphy
- onesenterprise
- paraiso-light
- pastie
- perldoc
- pygments
- solarized-light
- tango
- trac
- visual_studio
- vulcan
- xcode
- average
- base16snazzy
- catppuccin-frappe
- catppuccin-macchiato
- catppuccin-mocha
- doom-one
- doom-one2
- dracula
- fruity
- github-dark
- gruvbox
- monokai
- native
- paraiso-dark
- rrt
- solarized-dark
- solarized-dark256
- swapoff
- vim
- witchhazel
- xcode-dark
- jqq for inspiration
-
jqp uses https://github.com/atotto/clipboard for clipboard functionality. Things should work as expected with OSX and Windows. Linux, Unix require xclip or xsel to be installed. ↩
![Dyson Spheres are a joke [video]](https://www.youtube.com/img/desktop/supported_browsers/chrome.png)
