Updated Troubleshooting (markdown)

Marc Cornellà 2015-05-04 22:51:21 +02:00
parent 365bcbd90f
commit 72df1a8d03

@ -35,7 +35,7 @@ Many completion problems, including the infamous `command not found: compdef`, c
As a last resort, if you're getting weird behavior and can't find the culprit, run the following command to enable debug mode: As a last resort, if you're getting weird behavior and can't find the culprit, run the following command to enable debug mode:
```sh ```sh
zsh -xv 2> >(tee ~/omz-debug.log &>/dev/null) zsh -xv &> >(tee ~/omz-debug.log 2>/dev/null)
``` ```
Afterwards, reproduce the behavior (_i.e._ if it's a particular command, run it), and when you're done, run `exit` to stop the debugging session. Afterwards, reproduce the behavior (_i.e._ if it's a particular command, run it), and when you're done, run `exit` to stop the debugging session.
This will create a `omz-debug.log` file on your home directory, which you can upload to [gist.github.com](https://gist.github.com/) and link to it on the issue you'll open next. This will create a `omz-debug.log` file on your home directory, which you can upload to [gist.github.com](https://gist.github.com/) and link to it on the issue you'll open next.