Not trying to be stubborn or annoying, I still think that text-based logging would be a better way to do it. Maybe you could also implement selective logging of *everything*: only errors, scheduler, scripts, keys etc. Users would be able to select what they want to have logged, like in the export function. Logging other things than errors wouldn't be terribly useful to me, but i tmay be useful to others.
One more thing: if you happen to implement text-based logging, make each entry take no more than one single line, and separate things clearly, like this: date::time::event type::event Last error? Well, just open the file and examine it manually or parse the log file, get the last line and regex it to get the error. Just a suggestion. I'll come back here in a month or two to see what you folks decided. Ta-ta! -- Luciano ES Santos, SP - Brasil > <-quote-> ************************************************** On 10/11/04 at 17:16, brucexs wrote in 3K: >Too hard for me to do, as would be "preprocessing" commands to check >for errors before executing them. > >I will look at a new command >Exec puterrorto file/screen/both >command, which would set the output for errors to a file. >I can also start settings a global variables _lasterror_ to the >contents of the last message (which may be multi-line). ********* END OF ORIGINAL MESSAGE *********</-quote-> ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
