Skip to content

Commit

Permalink
Merge pull request #859 from tjex/docs
Browse files Browse the repository at this point in the history
docs: clarify directory defaults and environment variables
  • Loading branch information
denisidoro committed Dec 10, 2023
2 parents b560ba5 + d036487 commit a8f38db
Show file tree
Hide file tree
Showing 2 changed files with 26 additions and 0 deletions.
1 change: 1 addition & 0 deletions README.md
Expand Up @@ -90,6 +90,7 @@ The full syntax and examples can be found [here](docs/cheatsheet_syntax.md).
You can:

- [setup your own config file](docs/config_file.md)
- [set custom paths for your config file and cheat sheets](docs/paths_and_env_vars.md)
- [change colors](docs/customization.md#changing-colors)
- [resize columns](docs/customization.md#resizing-columns)
- [change how search is performed](docs/customization.md#overriding-fzf-options)
Expand Down
25 changes: 25 additions & 0 deletions docs/paths_and_env_vars.md
@@ -0,0 +1,25 @@
# Paths and Environment Variables

Navi uses the [`directories-next`](https://crates.io/crates/directories-next) package, which
defines platform-specific standard locations of directories for config, cache and other data.

Mac users, this is why your files are being stored in `~/Library/Application Support/navi`.

To set custom paths for your config and cheat sheets, you can set the following
environment variables:

```zsh
export NAVI_CONFIG="~/.config/navi/config.yaml"
export NAVI_PATH="~/.local/share/navi"
```
Despite `$NAVI_PATH` being set, it will not be used when installing cheat
sheets directly via navi's own commands.

For example when running `navi add repo <repo>`, the default paths as per the `directories-next`
package will still be used.

To avoid this, you may simply clone repos via a regular `git clone` command,
directly into `$NAVI_PATH`.

Note! `navi info cheats-path` and `navi info config-path` display the *default* path, not
the path set by the user. [It is known that this is a little misleading!](https://github.com/denisidoro/navi/issues/664#issuecomment-1004721178).

0 comments on commit a8f38db

Please sign in to comment.