How luadist/scite works
This tree is a partial source snapshot of SciTE, a Scintilla-based text editor, alongside an embedded Lua 5.1.4 runtime. The main user workflow is opening a file, editing it through Scintilla, and saving it; SciTE also exposes Lua extensions and background file work. The README documents GTK/Linux and Windows versions. The sampled source is limited, so links between unsampled editor subsystems are omitted; the Lua nodes reflect the runtime’s visible source layout rather than a fully traced call graph.
Main entry points: SciTEBase.h SciTE core · FileWorker.h File I/O · lua.h Lua C API · lstate.c Runtime state
Components 16
Editor
- SciTE core
src/SciTEBase.h - Platform UI
win32/SciTEWin.h - Scintilla editor
File work
- File I/O
src/FileWorker.h - Worker framework
src/Worker.h
Lua integration
- Lua extension
src/LuaExtension.h - Lua C API
lua/include/lua.h
Lua runtime
- Lexer
lua/src/llex.c - Parser
lua/src/lparser.c - Code generation
lua/src/lcode.c - Virtual machine
lua/src/lvm.c - Runtime state
lua/src/lstate.c - Standard libraries
lua/src/lib/linit.c - Module loading
lua/src/lib/loadlib.c
Other components
- Editor user
- Local files
Connections 13
- Editor user → Platform UI: operates
- Platform UI → SciTE core: handles UI
- SciTE core → Scintilla editor: editor operations
- SciTE core → File I/O: loads and saves
- File I/O → Local files: reads and writes
- File I/O → Worker framework: runs as
- Lua extension → Lua C API: uses API
- Lua C API → Runtime state: operates on
- Lexer → Parser: provides tokens
- Parser → Code generation: emits instructions
- Virtual machine → Runtime state: executes in
- Standard libraries → Lua C API: registers libraries
- Module loading → Runtime state: loads modules