Troubleshooting

First help

Run RESH doctor to detect common issues:

reshctl doctor

Restarting RESH daemon

Sometimes restarting RESH daemon can help:

resh-daemon-restart

You can also start and stop RESH daemon with:

resh-daemon-start
resh-daemon-stop

⚠️ You will get error messages in your shell when RESH daemon is not running.

Recorded history

Your RESH history is saved in one of:

~/.local/share/resh/history.reshjson
$XDG_DATA_HOME/resh/history.reshjson

Each line is one JSON record prefixed by version. Display it as JSON using:

cat ~/.local/share/resh/history.reshjson | sed 's/^v[^{]*{/{/' | jq .

ℹ️ You will need jq installed.

Configuration

RESH config is read from one of:

~/.config/resh.toml
$XDG_CONFIG_HOME/resh.toml

Logs

Logs can be useful for troubleshooting issues.

Find RESH logs in one of:

~/.local/share//resh/log.json
$XDG_DATA_HOME/resh/log.json

Log verbosity

Get more detailed logs by setting LogLevel = "debug" in RESH config.
Restart RESH daemon for the config change to take effect: resh-daemon-restart

Common problems

Using RESH with bash on macOS

ℹ️ It is recommended to use zsh on macOS.

MacOS comes with really old bash (bash 3.2).
Update it using: brew install bash

On macOS, bash shell does not load ~/.bashrc because every shell runs as login shell.
Fix it by running: echo '[ -f ~/.bashrc ] && . ~/.bashrc' >> ~/.bash_profile

GitHub issues

Problem persists? Create an issue ⇗

1.6 KiB Raw Blame History Unescape Escape