On Wed, Nov 25, 2009 at 11:04:32PM +1030, David Kettler wrote: > >Those errors are dumped to the console by conkeror, not xulrunner. See > >utils.js, console_service.registerListener... > > Okay, thanks. > > >I find it helpful to see > >content javascript errors on the console. Do you have another idea? > > I'm mostly interested in errors from conkeror, but usually not from > content over which I have no control. Mainly I don't want to miss > seeing a conkeror error because I'm ignoring other crap. > > Usually I run conkeror from the command line so that errors just end > up in my terminal. Simply redirecting output to a file that I > occasionally inspect will probably fix the problem for me. Two > other suggestions: > > Put content errors in a log file, separate from conkeror errors. > > Have much terser errors on the output. Put details in a log file. > > But if others aren't bothered, I'll just change my habits. > > regards, David
Please open a thread about this on bugs.conkeror.org and we can collect ideas for better ways to deal with errors, warnings and messages. This is the kind of thing that could easily turn into a huge project involving the creation of a *Messages* buffer, user-configurable streams for different log levels, et cetera. -- John Foerch _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
