On Tue, Oct 25, 2011 at 10:48 PM, ne1uno <[email protected]> wrote: > the optparse docs effectively hid from me any hint of extra options or > turning off errors on non existent options. > so I wasn't able to actually try --style or --stylesheet
Leo support neither --style nor --stylesheet at present. > I see now that --stylesheet would have to be intercepted, > I doubt the one given on the command line would override > any stylesheet set programmaticly by Leo. In fact, Leo will handle these command-line arguments, so Leo will be able to do anything with the argument it likes, including overriding whatever @data qt-gui-plugin-style-sheet is in effect. This would be the expected way. > config files are a little problematic. when they error, Leo will > print an error message and exit python taking the command > prompt down with it Leo will execute the config file inside a try/except block, so Leo will be able to recover from errors in ~/.leo_config.py without fuss. > not limited to problems in a config file, > some python errors before Leo gets rolling will pause the display if > started with python -i launchLeo, > but disappear as well if using pythonw. Not a problem. All messages to Leo's log get queued during startup for display once the log pane exists. > it would be nice if python would trap all errors. Python does "trap" all errors. It's up to the Python code to catch thrown exceptions. Leo does a pretty good job of catching all errors. The only errors that will take Leo down are syntax errors in Leo's core. I usually find those quickly enough ;-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
