There are currently two different directories in which Quadtastic tries to find exporters. S.exporters_dirname, which is rooted in the Quadtastic source directory, contains the built-in exporters, and S.custom_exporter_dirname -- a directory somewhere in the user's home directory where custom exporters can be stored without having to mess with Quadtastic's source directory.
exporters.list is called from two places in the code: once in main.lua on start-up, and in reload_exporters.
In main.lua, it is called with both, the directory for built-in exporters, and the directory for custom exporters:
76 -- Fetch exporters
77 local list_success, more = pcall(exporters.list,
78 {S.exporters_dirname, S.custom_exporters_dirname})
In reload_exporters, S.custom_exporter_dirname is missing, so that the 'Reload exporters' menu entry doesn't actually scan the directory that contains custom exporters.
There are currently two different directories in which Quadtastic tries to find exporters.
S.exporters_dirname, which is rooted in the Quadtastic source directory, contains the built-in exporters, andS.custom_exporter_dirname-- a directory somewhere in the user's home directory where custom exporters can be stored without having to mess with Quadtastic's source directory.exporters.listis called from two places in the code: once inmain.luaon start-up, and inreload_exporters.In
main.lua, it is called with both, the directory for built-in exporters, and the directory for custom exporters:In
reload_exporters,S.custom_exporter_dirnameis missing, so that the 'Reload exporters' menu entry doesn't actually scan the directory that contains custom exporters.