xinb
/
ohmyzsh
mirror of https://github.com/ohmyzsh/ohmyzsh.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Make the trace command more useful

Marc Cornellà 2022-06-05 16:05:59 +02:00 committed by GitHub
parent 30c68ee162
commit d6898621a6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Troubleshooting.md

@ -51,10 +51,10 @@ 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:
```sh
zsh -xv &> >(tee ~/omz-debug.log 2>/dev/null)
zsh -xv 2> >(tee ~/omz-debug.log &>/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. 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.
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, with a trace of every command executed and its output. You can then upload this file when creating an issue.
If you only need to debug the session initialization, you can do so with the command: