Hi again, On Sat, Feb 13, 2010 at 07:11:26PM +0100, Luca Capello wrote: > Second, the error should be a warning and thus the rcfile should > be read until the end.
Upstream agrees partially. The reasoning is that as with Emacs where you should be able to edit your .emacs even if it's broken, with Conkeror you should be able to visit http://conkeror.org/BreakingChanges even if your conkerorrc is broken. So Conkeror should not stop it's own execution on such errors (was another suggestion, too). But xulrunner doesn't seem to provide a possibility to continue the execution of a JS file if there is an error in it, so upstream can't do much about it. Emacs seems to behave that way, too, btw. And I also think that it might be dangerous if an error doesn't stop evaluating the configuration, because the configuration is a script and is possibly harmful if parts are not working correctly and later parts are executed nevertheless. It at least would often cause following errors which are gone if the first error is gone. In case of syntactic error it's also quite difficult to correctly find the right place where to continue executing the code. There is though a *Messages* buffer (like in Emacs) planned to show such issues. Work already started on it but is not yet published. http://bugs.conkeror.org/issue232 is now marked as "in progress". :-) Regards, Axel -- Axel Beckert - [email protected], [email protected] - http://noone.org/abe/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
