From 77b350dcbf961d88c0ccf1a6282e2e2955091c13 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C5=A0imon=20Let?= Date: Mon, 30 Jan 2023 21:47:20 +0100 Subject: [PATCH] Update troubleshooting.md --- troubleshooting.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/troubleshooting.md b/troubleshooting.md index af22a8f..5a11bf8 100644 --- a/troubleshooting.md +++ b/troubleshooting.md @@ -14,7 +14,7 @@ Sometimes restarting RESH daemon can help: resh-daemon-restart ``` -Two more useful commands: +You can also start and stop RESH daemon with: ```sh resh-daemon-start resh-daemon-stop @@ -26,7 +26,7 @@ resh-daemon-stop Your RESH history is saved in one of: - `~/.local/share/resh/history.reshjson` -- `${XDG_DATA_HOME/resh/history.reshjson` +- `$XDG_DATA_HOME/resh/history.reshjson` The format is JSON prefixed by version. Display it as json using: @@ -40,7 +40,7 @@ You will need `jq` installed. RESH config is read from one of: - `~/.config/resh.toml` -- `${XDG_CONFIG_HOME}/resh.toml` +- `$XDG_CONFIG_HOME/resh.toml` ## Logs @@ -48,10 +48,12 @@ Logs can be useful for troubleshooting issues. Find RESH logs in one of: - `~/.local/share//resh/log.json` -- `${XDG_DATA_HOME}/resh/log.json` +- `$XDG_DATA_HOME/resh/log.json` -You can get more detailed logs by setting `logLevel = "debug"` in `~/.config/resh.toml` +### Log verbosity +Get more detailed logs by setting `LogLevel = "debug"` in [RESH config](#configuration). +Restart RESH daemon for the config change to take effect: `resh-daemon-restart` ## Common issues @@ -62,3 +64,7 @@ Update it using: `brew install bash` On macOS, bash shell does not load `~/.bashrc` because every shell runs as login shell. Run `echo '[ -f ~/.bashrc ] && . ~/.bashrc' >> ~/.bash_profile` + +## Github issues + +Problem persists? [Create an issue ⇗](https://github.com/curusarn/resh/issues)