From b391509be66f5c281f8dd0f557db3c17fa088ae5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Djk=C3=A1=C5=A5o?= Date: Wed, 7 Jun 2023 14:48:27 +0200 Subject: [PATCH] Update troubleshooting.md Added `2> log_err.txt` to the command and explained what it does. This is necessary as stderr will otherwise get outputted to the console instead of the file. --- content/lua.scripts.manual/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/lua.scripts.manual/troubleshooting.md b/content/lua.scripts.manual/troubleshooting.md index 515b911..afdb343 100644 --- a/content/lua.scripts.manual/troubleshooting.md +++ b/content/lua.scripts.manual/troubleshooting.md @@ -22,4 +22,4 @@ Open a terminal and start darktable with the command `/Applications/darktable.ap ### Windows -Open a command prompt. Start darktable with the command "C:\Program Files\darktable\bin\darktable" -d lua > log.txt. This provides debugging information to give you insight into what is happening. +Open a command prompt. Start darktable with the command `"C:\Program Files\darktable\bin\darktable" -d lua > log.txt 2> log_err.txt`. `stdout`, which contains regular output of commands like `print()` will get printed into the `log.txt` file. `stderr`, which contains program errors will get saved inside `log_err.txt` file. This provides debugging information to give you insight into what is happening.