djkato/luadocs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update troubleshooting.md

Browse source 
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.
This commit is contained in:
Djkáťo 2023-06-07 14:48:27 +02:00 committed by GitHub
parent 01c6453c10
commit b391509be6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/lua.scripts.manual/troubleshooting.md
View file

@ -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.