Troubleshooting

First help

Run RESH doctor to detect common issues:

reshctl doctor

Restarting RESH daemon

Sometimes restarting RESH daemon can help:

resh-daemon-restart

Two more useful commands:

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

The format is JSON 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

You can get more detailed logs by setting logLevel = "debug" in ~/.config/resh.toml

Common issues

Using RESH in bash 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.
Run echo '[ -f ~/.bashrc ] && . ~/.bashrc' >> ~/.bash_profile

1.3 KiB Raw Blame History Unescape Escape