luadocs/content/lua.scripts.manual/troubleshooting.md
Djkáťo 92761ec090
change 2>log_err.txt to 2>&1
redicrects the sterr to stdout so it can all be in the same file
2023-06-07 17:04:40 +02:00

25 lines
972 B
Markdown

---
title: troubleshooting
id: troubleshooting
weight: 30
draft: false
author: "people"
---
Running darktable with Lua debugging enabled provides more information about what is occurring within the scripts.
### Snap
Open a terminal and start darktable with the command `snap run darktable -d lua`. This provides debugging information to give you insight into what is happening.
### Linux
Open a terminal and start darktable with the command `darktable -d lua`. This provides debugging information to give you insight into what is happening.
### MacOS
Open a terminal and start darktable with the command `/Applications/darktable.app/Contents/MacOS/darktable -d lua`. This provides debugging information to give you insight into what is happening.
### Windows
Open a command prompt. Start darktable with the command `"C:\Program Files\darktable\bin\darktable" -d lua > log.txt 2>&1`. This provides debugging information to give you insight into what is happening.