On Sun, Feb 7, 2010 at 11:34, Shawn Skriver <[email protected]> wrote:
> > > On Sun, Feb 7, 2010 at 11:31, Shawn Skriver <[email protected]>wrote: > >> >> >> On Sun, Feb 7, 2010 at 11:14, Edward K. Ream <[email protected]> wrote: >> >>> On Sun, Feb 7, 2010 at 10:46 AM, Edward K. Ream <[email protected]> >>> wrote: >>> >>> I was not able to exercise this code without enabling the open_with >>> plugin. >>> >>> The best way to discover whether a plugin is present is to do >>> <alt-x>print-plugins-info<return> >>> >>> Obviously, Leo should not have crashed in any case. Rev 2900 contains >>> some changes that may help: >>> >>> 1. The open_with plugin now demands that the Tk gui be present. This >>> probably will prevent the open_with plugin from loading unless Tk is, >>> in fact, the active gui. >>> >>> 2. I made an *untested* change to c.openWithTempFilePath that will >>> prevent the proximate cause of the crash you cite. >>> >>> Please report any further problems immediately. Thanks. >>> >>> Edward >>> >>> >> Response using 'print-plugins-info': > > colorize_headlines myLeoSettings.leo > leo_to_html myLeoSettings.leo > vim myLeoSettings.leo > plugins_menu myLeoSettings.leo > mod_scripting myLeoSettings.leo > UNL myLeoSettings.leo > > A "quick and dirty" check by removing ALL of the content of myLeoSettings.leo's @enabled-plugins eliminates the exception. I will try to find out which of the my non-standard plugin selections (vim.py or colorize_headlines.py) seems to cause the exception. -Shawn -- 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.
