FileActions plugin: [EMAIL PROTECTED] type node bug?
FileActions' onIconDoubleClick method attempts to process non @file type nodes. This generates an error (see end of posting). I would expect FileActions to ignore @file type nodes to avoid a conflict with my use of the open with plugin. I added the following code to the onIconDoubleClick to solve the problem: if p.isAnyAtFileNode(): return Is this a bug (if so, I'm surprised it hasn't been caught before)? Regards, TL Error dump to Log: Traceback (most recent call last): File C:\Program Files\_Progs\Leo\src\leoGlobals.py, line 2530, in doHook return f(tag,keywords) File C:\Program Files\_Progs\Leo\src\leoPlugins.py, line 91, in doPlugins return doHandlersForTag(tag,keywords) File C:\Program Files\_Progs\Leo\src\leoPlugins.py, line 70, in doHandlersForTag val = callTagHandler(bunch,tag,keywords) File C:\Program Files\_Progs\Leo\src\leoPlugins.py, line 49, in callTagHandler result = handler(tag,keywords) File C:\Program Files\_Progs\Leo\plugins\FileActions.py, line 123, in onIconDoubleClick filename = words[1] IndexError: list index out of range --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Leo 4.4.8 is feature frozen
On Apr 4, 9:08 am, Edward K. Ream [EMAIL PROTECTED] wrote: And I just discovered another bug: the 'Find' button in the Spell tab has a major performance bug when both the 'Search Body' and 'Search Headline' checkboxes are selected in the *Find* tab. I'll fix this immediately. OMG, I just fixed a *stupendous* performance bug in the find/spell tabs. The code that collapsed nodes used c.allNodes_iter! The new code just looks collapses the ancestors of the previously selected node. The effect is amazing: Leo's find command now appears to work instantaneously. We haven't complained until now because the old code, buggy as it was, was actually a considerable improvement over the old way that left more and more nodes expanded in the outline. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Leo 4.4.8 is feature frozen
I take it you've begun looking at my code :-) On Apr 4, 10:55 am, Edward K. Ream [EMAIL PROTECTED] wrote: On Apr 4, 9:08 am, Edward K. Ream [EMAIL PROTECTED] wrote: And I just discovered another bug: the 'Find' button in the Spell tab has a major performance bug when both the 'Search Body' and 'Search Headline' checkboxes are selected in the *Find* tab. I'll fix this immediately. OMG, I just fixed a *stupendous* performance bug in the find/spell tabs. The code that collapsed nodes used c.allNodes_iter! The new code just looks collapses the ancestors of the previously selected node. The effect is amazing: Leo's find command now appears to work instantaneously. We haven't complained until now because the old code, buggy as it was, was actually a considerable improvement over the old way that left more and more nodes expanded in the outline. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
found mistake in docs ch. 3
the rst markup is: - ``F20` (``Cut`` on many Sun workstations) or ``Control-x`` copies the selection in the widget to the clipboard and deletes the selection. These keys have no effect if no text is selected. and should be - ``F20`` (``Cut`` on many Sun workstations) or ``Control-x`` copies the selection in the widget to the clipboard and deletes the selection. These keys have no effect if no text is selected. in @rst html\outlines.html -- Editing body text Noticed it by the highlighting difference when studying the LeoDocs.leo code. John Griessen --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Unit testing problem
Hi fellow Leo enthusiasts, I am playing with unit testing some of my python code. I created two buttons: test and run-all-tests. The code is as follows: === test === import leoTest leoTest.doTests(c, all=False) === end test === === run-all-tests === import leoTest leoTest.doTests(c, all=True) === end run-all-tests === The test button works as expected, but run-all-tests produces the following output in the Log pane: exception executing script AttributeError: 'NoneType' object has no attribute 'v' line 1270: return ( * line 1271: p1.v == p2.v and line 1272: p1.stack == p2.stack and line 1273: p1.childIndex() == p2.childIndex()) I am running the latest code from bzr. ---Kayvan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
Re: Unit testing problem
I think I saw the same thing doing Alt-4 in the unitTest.leo file, but my screen saver had fired off in the middle of the tests, and I attributed it to an errant extra mouse click, since when I lengthened the screen saver timeout and the test ran uninterrupted, the problem did not recur. If you're seeing it repeatably, then you've got something different. - Stephen On Apr 4, 4:49 pm, Kayvan A. Sylvan [EMAIL PROTECTED] wrote: Hi fellow Leo enthusiasts, I am playing with unit testing some of my python code. I created two buttons: test and run-all-tests. The code is as follows: === test === import leoTest leoTest.doTests(c, all=False) === end test === === run-all-tests === import leoTest leoTest.doTests(c, all=True) === end run-all-tests === The test button works as expected, but run-all-tests produces the following output in the Log pane: exception executing script AttributeError: 'NoneType' object has no attribute 'v' line 1270: return ( * line 1271: p1.v == p2.v and line 1272: p1.stack == p2.stack and line 1273: p1.childIndex() == p2.childIndex()) I am running the latest code from bzr. ---Kayvan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com 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 -~--~~~~--~~--~--~---
