Re: Best way to get window/frame for current leo file
On Fri, May 29, 2015 at 3:33 PM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote: c.frame or some attribute of c.frame? Or walk c.frame.parent() until None, or the better answer Edward will provide ;-) c.frame is almost always what is wanted. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: goto-global-line doesn't work properly in @clean files
On Tuesday, June 2, 2015 at 9:22:00 AM UTC-5, vitalije wrote: I presume Edward missed this topic, so I am just touching it again. IMHO this bug can easily repel newbies. If one is not able after seeing stack trace in console, to easily find a specific line in source code using Leo, he could get very wrong impression about Leo's capabilities. Thanks for the reminder. The two bugs related to @clean, #150 https://github.com/leo-editor/leo-editor/issues/150 and #193 https://github.com/leo-editor/leo-editor/issues/193 have top priority. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Implementing goto-next-N-visible
On Sat, Jun 6, 2015 at 10:08 AM, 'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote: On Fri, 5 Jun 2015 11:01:13 -0500 'Terry Brown' via leo-editor leo-editor@googlegroups.com wrote: Well, I'm definitely seeing Todo.py related slow down, and will attempt to investigate that. Just pushed a fix for this. w.setStyle(/* */) was being called on every node, and is just too slow for that :-/ Now it's called on idle, which was tricky [snip] Thanks for this. Here is what I think I know about loading large text. 1. Syntax coloring: At present, the Python colorizer is enabled in leoColorizer.py. That is, python_qsh = True. This switch enables idle-time colorizing of the text, so the length of text shouldn't matter. 2. Waiting for large text to load. Qt has major issues with large text. This should not cause problems if the user doesn't try to change the text. The setting, @int max-pre-loaded-body-chars = 3, controls whether Leo will insert so-call large-text buttons for body text greater than the given value. (The value of 0 disables the feature). I doubt whether much more can be done to speed loading of large text. The normal workaround is to split large nodes. HTH. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: @command nodes not dynamically updated
On Mon, Jun 1, 2015 at 6:22 AM, john lunzer lun...@gmail.com wrote: About a month ago Terry posted about how the dynamic nature of @button/@rclick/@command nodes and how powerful that concept is. When I define commands in my myLeoSettings.leo @settings--@commands node I'm not seeing this dynamic behavior. If I change code in one of these @command mycmd nodes I have to restart Leo for the code to update. That said @button nodes or buttons created from the script-button button are dynamic and they are awesome and powerful. Somebody let me know what I'm doing wrong. Are they only dynamic for local @commands? My apologies for the delay in responding. The fix for #171 https://github.com/leo-editor/leo-editor/issues/171 does indeed freeze non-local @command and @button nodes. The notes give detailed rationale for this behavior. It isn't going to change. The workaround is to test scripts using local @button/@command nodes. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: mistake in the documentation
On Wed, May 20, 2015 at 5:12 AM, Zoltan Benedek benzol...@gmail.com wrote: The algorithm always places ambiguous lines at the start of the following node because it’s more common to add lines to the end of nodes. Probably should be: The algorithm always places ambiguous lines at the end of the previous node because it’s more common to add lines to the end of nodes. Good catch. Thanks. Fixed in LeoDocs.leo and on the web page. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Adding my change to body text to the undo stack
On Mon, Jun 1, 2015 at 7:40 AM, john lunzer lun...@gmail.com wrote: I'm working on a command that makes a change to c.p.b. If I make that change simply by assigning a string to c.p.b I can't use Ctrl+Z to undo the change. How would I go about making my command undo enabled? My apologies for the delay in responding. The general ideas are in LeoDocs.leo: LeoDocs.leo#Leo's Documentation--Advanced Topics--A scripting miscellany--@rst html\scripting-miscellany.html--Making operations undoable Leo's sources contain many examples of the various patterns involved. When I want to make something undoable, I use the undo code in a similar command as a guide. HTH. Feel free to ask more questions here. I'll answer them promptly. EKR -- You received this message because you are subscribed to the Google Groups leo-editor group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.