Lua Error log (in Linux)
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Lua Error log (in Linux)

Started by Dessamator, 15 February, 2012, 08:47:35

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Dessamator

Hi,

I was recently attempting to debug a script in Linux, and apparently the error log is not created for anything beside "System.log".   I assume I'm ignorant of some setting or perhaps some configuration that needs to be done, but it compiled successfully, and runs all scripts.

Except for a small change i made in the make file, it seemed to reference lua5.1, and in my Fedora Core 16 system, it was just "lua", after the change it compiled successfully.

Is there any setting or command to force Ptokax to output the errors to a file?


Ignorance is Bliss.

the-master

Plz read the scripting interface before posting, your answer is right before you..
its in the Settings bool IDs forSetMan.(G/S)etBool number 55, can be enabled with a simple script
function OnStartup()
                   	SetMan.SetBool(55,1)
	SetMan.Save()
end

running once will do the trick ;-)
keep on sharing :)

Dessamator

#2
Quote from: the-master on 15 February, 2012, 10:17:11
Plz read the scripting interface before posting, your answer is right before you..
its in the Settings bool IDs forSetMan.(G/S)etBool number 55, can be enabled with a simple script
function OnStartup()
                   	SetMan.SetBool(55,1)
	SetMan.Save()
end

running once will do the trick ;-)

Ignorance is indeed bliss.

Thanks, sounds like something I would have said in the past. Anyway, it was never( as far as I can see) posted in the forum, and so should theoretically  help others too.

PS:   I'm not sure if it was something I was doing wrong or not. But it seemed to work after I changed it to :
SetMan.SetBool(55,true)

Ignorance is Bliss.

the-master

it is inhere.. and mutor made a script with bits of explaining ;-)
http://forum.ptokax.org/index.php?topic=7244#msg69760
keep on sharing :)

Dessamator

Quote from: the-master on 15 February, 2012, 11:18:11

it is inhere.. and mutor made a script with bits of explaining ;-)
http://forum.ptokax.org/index.php?topic=7244#msg69760


To quote myself again, ignorance is indeed bliss.

Thanks, you are in fact correct, I've just not been updated on new Px versions  and the forum for many years, and this is the result.
Ignorance is Bliss.

the-master

keep on sharing :)

SMF spam blocked by CleanTalk