Each line is a JSON that represents one executed command line.
Each line is a versioned JSON that represents one executed command line.
This is how I view it `tail -f ~/.resh_history.json | jq` or `jq < ~/.resh_history.json`.
You can install `jq` using your favourite package manager or you can use other JSON parser to view the history.
You can install `jq` using your favorite package manager or you can use other JSON parser to view the history.

@ -115,13 +117,13 @@ You can install `jq` using your favourite package manager or you can use other J
### Q: I use bash on macOS and resh doesn't work
**A:** You have to add`[ -f ~/.bashrc ] && . ~/.bashrc` to your `~/.bash_profile`.
**A:** Add line`[ -f ~/.bashrc ] && . ~/.bashrc` to your `~/.bash_profile`.
**Long Answer:** Under macOS bash shell only loads `~/.bash_profile` because every shell runs as login shell. I will definitely work around this in the future but since this doesn't affect many people I decided to not solve this issue at the moment.
**Long Answer:** Under macOS bash shell only loads `~/.bash_profile` because every shell runs as login shell.
## Issues and ideas
Please do create issues if you encounter any problems or if you have a suggestions: https://github.com/curusarn/resh/issues
Please do create issues if you encounter any problems or if you have suggestions: https://github.com/curusarn/resh/issues
fmt.Fprintf(os.Stderr,"\nWARN: Resh-daemon is running in different version than is installed now - it looks like something went wrong during resh update.\n\n")
fmt.Fprintf(os.Stderr,"-> Kill resh-daemon and then launch a new terminal window to fix that.\n")
fmt.Fprintf(os.Stderr," $ pkill resh-daemon\n")
fmt.Fprintf(os.Stderr,"-> You can file an issue at: https://github.com/curusarn/resh/issues\n")
fmt.Fprintf(os.Stderr,"\nWARN: This terminal session was started with different resh version than is installed now - it looks like you updated resh and didn't restart this terminal.\n\n")
fmt.Fprintf(os.Stderr,"-> Restart this terminal window to fix that.\n")