From 78a0b24eee3b0369425c4f1717725e36a4e03779 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcel=20St=C3=B6r?= Date: Sun, 15 Mar 2020 09:39:33 +0100 Subject: [PATCH] Fix init.lua link --- docs/lua-developer-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/lua-developer-faq.md b/docs/lua-developer-faq.md index b7af9b7a..5ae459f4 100644 --- a/docs/lua-developer-faq.md +++ b/docs/lua-developer-faq.md @@ -88,7 +88,7 @@ There are standard libraries to provide access to the various hardware options s The runtime system runs in interactive-mode. In this mode it first executes any `init.lua` script. It then "listens" to the serial port for input Lua chunks, and executes them once syntactically complete. -There is no batch support, although automated embedded processing is normally achieved by setting up the necessary event triggers in the [`init.lua`](../upload/#initlua) script. +There is no batch support, although automated embedded processing is normally achieved by setting up the necessary event triggers in the [`init.lua`](upload.md#initlua) script. The various libraries (`net`, `tmr`, `wifi`, etc.) use the SDK callback mechanism to bind Lua processing to individual events (for example a timer alarm firing). Developers should make full use of these events to keep Lua execution sequences short.