That could make sense - something like 'SciteStartup.lua', sitting in
the 'appropriate' directory for Windows and Linux. I tend to use
different script placement strategies on Windows because the user
directories are in such awkward places. It would IMHO also be useful
if SciTE gave a friendlier
Are you running 1.73 with the debugger?
On 7/20/07, Richard Heyes [EMAIL PROTECTED] wrote:
Hi,
I get the following error when starting Scite:
attempt to call a string value
Lua: error occurred while loading startup script
attempt to call a string value
Lua: error occurred while loading
Sorry, it doesn't matter what version you're running - I don't think.
SciTE is looking for something eg:
ext.lua.startup.script=$(SciteDefaultHome)\scite-gdb\extman.lua
Tells it to load extman.lua, if it doesn't exist then you get that error.
This is the line I use to load the debugger so it's
James Cuénod:
Sorry, it doesn't matter what version you're running - I don't think.
SciTE is looking for something eg:
ext.lua.startup.script=$(SciteDefaultHome)\scite-gdb\extman.lua
Maybe it would be simpler if SciTE had a preferred script name and
ext.lua.startup.script was just a way
Hi,
I get the following error when starting Scite:
attempt to call a string value
Lua: error occurred while loading startup script
attempt to call a string value
Lua: error occurred while loading startup script
What's the startup script called?
Thanks.
--
Richard Heyes
+44 (0)844 801 1072
