# navi icon [![CircleCI](https://circleci.com/gh/denisidoro/navi.svg?style=svg)](https://circleci.com/gh/denisidoro/navi) ![GitHub release (latest by date including pre-releases)](https://img.shields.io/github/v/release/denisidoro/navi?include_prereleases) An interactive cheatsheet tool for the command-line so that you'll never say the following again: >— *How to run that command again?*
— *Oh, it's not in my bash history*
— *Geez, it's almost what I wanted but I need to change some args* ![Demo](https://user-images.githubusercontent.com/3226564/65389667-0181dc80-dd2f-11e9-9fac-c875ed7c7b53.gif) **navi** allows you to browse through cheatsheets (that you may write yourself or download from maintainers) and execute commands, prompting for argument values. Table of Contents ----------------- * [Installation](#installation) * [Using Homebrew or Linuxbrew](#using-homebrew-or-linuxbrew) * [Using git](#using-git) * [Upgrading](#upgrading) * [Usage](#usage) * [Preventing execution](#preventing-execution) * [Pre-filtering](#pre-filtering) * [Searching online repositories](#searching-online-repositories) * [More options](#more-options) * [Trying out online](#trying-out-online) * [Motivation](#motivation) * [Cheatsheets](#cheatsheets) * [Using your own custom cheatsheets](#using-your-own-custom-cheatsheets) * [Submitting cheatsheets](#submitting-cheatsheets) * [Cheatsheet syntax](#cheatsheet-syntax) * [Syntax overview](#syntax-overview) * [Variables](#variables) * [FZF options](#fzf-options) * [Related projects](#related-projects) * [Etymology](#etymology) Installation ------------ ### Using Homebrew or Linuxbrew You can use [Homebrew](http://brew.sh/) or [Linuxbrew](http://linuxbrew.sh/) to install **navi**: ```sh brew install denisidoro/tools/navi ``` ### Using git Alternatively, you can `git clone` this repository and run `make`: ```sh git clone --depth 1 http://github.com/denisidoro/navi /opt/navi cd /opt/navi sudo make install # install fzf: https://github.com/junegunn/fzf ``` Upgrading --------- **navi** is being actively developed and you might want to upgrade it once in a while. Please follow the instruction below depending on the installation method used: - brew: `brew update; brew reinstall navi` - git: `cd /opt/navi && sudo make update` Usage ----- By simply running `navi` you will be prompted with the default cheatsheets. ### Preventing execution If you run `navi --print`, the selected command won't be executed. It will be printed to stdout instead. ### Pre-filtering If you run `navi query `, the results will be pre-filtered. ### Searching online repositories If you run `navi search `, **navi** will try to download cheatsheets from online repositories as well. Please note that these cheatsheets aren't curated by **navi**'s maintainers and should be taken with a grain of salt. If you're not sure about executing these commands, make sure to check the preview window or use the `--print` option. ### More options Please refer to `navi --help` for more details. Trying out online -------------------- If you don't have access to bash at the moment and you want to live preview **navi**, head to [this playground](https://www.katacoda.com/denisidoro/scenarios/navi). It'll start a docker container with instructions for you to install and use the tool. Note: login required. Motivation ---------- The main objectives are: - to increase discoverability, by finding commands given keywords or descriptions; - to prevent you from running auxiliar commands, copying the result into the clipboard and then pasting into the original command; - to easily share one-liners with others so that they don't need to figure out how to write the commands; - to improve terminal usage as a whole. Sure, you can find autocompleters out there for all your favorite commands. However, they are very specific and each one may offer a different learning curve. Or you can launch a browser and search for instructions on Google, but that takes some time. **navi**, on the other hand, intends to be a general purpose platform for bookmarking any command at a very low cost. Cheatsheets ----------- ### Using your own custom cheatsheets In this case, you need to pass a `:`-separated list of separated directories which contain `.cheat` files: ```sh navi --path "/folder/with/cheats" ``` Alternatively, you can set an environment variable in your `.bashrc`-like file: ```sh export NAVI_PATH="/folder/with/cheats:/another/folder" ``` ### Submitting cheatsheets Feel free to fork this project and open a PR for me to include your contributions. Cheatsheet syntax ----------------- Cheatsheets are described in `.cheat` files. ### Syntax overview - lines starting with `%` should contain tags which will be added to any command in a given file; - lines starting with `#` should be descriptions of commands; - lines starting with `$` should contain commands that generate a list of possible values for a given argument; - all the other non-empty lines are considered as executable commands. For example, this is a valid `.cheat` file: ```sh % git, code # Change branch git checkout $ branch: git branch | awk '{print $NF}' ``` ### Variables The interface prompts for variable names inside brackets (eg ``). The command for generating possible inputs can refer other variables: ```sh # If you select 2 for x, the possible values of y will be 12 and 22 echo $ x: echo -e '1\n2\n3' $ y: echo -e "$((x+10))\n$((x+20))" ``` ### FZF options You can make pick a specific column of a selection and set the number of lines considered as headers: ```sh # This will pick the 3rd column and use the first line as header docker rmi $ image_id: docker images --- --headers 1 --column 3 ``` Related projects ---------------- There are many similar projects out there ([bro](https://github.com/hubsmoke/bro), [eg](https://github.com/srsudar/eg), [cheat.sh](https://github.com/chubin/cheat.sh), [tldr](https://github.com/tldr-pages/tldr), [cmdmenu](https://github.com/amacfie/cmdmenu), [cheat](https://github.com/cheat/cheat), [beavr](https://github.com/denisidoro/beavr), [how2](https://github.com/santinic/how2) and [howdoi](https://github.com/gleitz/howdoi), to name a few). Most of them provide excellent cheatsheet repositories, but lack a nice UI. In any case, **navi** has the option to [search for some of these repositories](#searching-online-repositories). Etymology --------- In [The Legend of Zelda Ocarina of Time](https://zelda.gamepedia.com/Ocarina_of_Time), [navi](https://zelda.gamepedia.com/Navi) is a character that provides [Link](https://zelda.gamepedia.com/Link) with a variety of clues to help him solve puzzles and progress in his quest.