From d6898621a635e627ff97891862a7a841128f71b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc=20Cornell=C3=A0?= Date: Sun, 5 Jun 2022 16:05:59 +0200 Subject: [PATCH] Make the trace command more useful --- Troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 22e25cb..7d0f31e 100644 --- a/Troubleshooting.md +++ b/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: