Re: When using LeoBridge, leoG.IdleTime() always returns None

On Saturday, January 27, 2018 at 1:44:08 PM UTC-8, SegundoBob wrote: > > g.app.gui.idleTimeClass is None so leoG.IdleTime() always returns None. > > Is this a recognized limitation? Is this limitation necessary? > > The Leo-Babel plugin I'm writing uses leoG.IdleTime(). I would like to > test

When using LeoBridge, leoG.IdleTime() always returns None

g.app.gui.idleTimeClass is None so leoG.IdleTime() always returns None. Is this a recognized limitation? Is this limitation necessary? The Leo-Babel plugin I'm writing uses leoG.IdleTime(). I would like to test my Leo-Babel plugin with a script using Leo-Babel. Thanks, SegundoBob -- You

Re: 04ef7c: git-diff command is safe and useful

On Sat, Jan 27, 2018 at 2:24 PM, tscv11 wrote: > Just a note: > > Thank-you: I fell in love with this command on first use! This is > now my favorite way of looking at my changes, and it provides > even more proof that everything is better "Leo style." > ​You're welcome.

Re: 04ef7c: git-diff command is safe and useful

Just a note: Thank-you: I fell in love with this command on first use! This is now my favorite way of looking at my changes, and it provides even more proof that everything is better "Leo style." tscv11 -- You received this message because you are subscribed to the Google Groups "leo-editor"

Re: master is now open. Leo 5.7b1 will be delayed

On Sat, Jan 27, 2018 at 7:09 AM, Edward K. Ream wrote: > Please feel free to commit to the master branch. > > Let's delay 5.7b1 for at least a few days while we work on PyPi and > installation instructions. There is no rush, and it's supremely important > to do as well as we

master is now open. Leo 5.7b1 will be delayed

Please feel free to commit to the master branch. Let's delay 5.7b1 for at least a few days while we work on PyPi and installation instructions. There is no rush, and it's supremely important to do as well as we can with installation docs and tools. Edward -- You received this message because

Re: Summary of installation discussions

On Sat, Jan 27, 2018 at 6:40 AM, Edward K. Ream wrote: Would you be willing to a .leo file that contains proposed text, with the > logical structure of the text mirrored in the node structure? > ​... > > You can use any convenient markup, including markdown, to indicate

Re: Summary of installation discussions

On Sun, Dec 10, 2017 at 6:13 AM, lewis wrote: > *Installing Leo* > > ​[snip]​ > *Quick and easy* > > [snip]​ > *Install Leo using pip* > ​[snip]​ > *Running Leo* > ​ [snip]​ *Options for installing Leo.* > ​ [snip]​ > *Dependencies* > ​[snip] ​ > *Installing

Re: Matt, what's the status of #562?

On Sat, Jan 27, 2018 at 3:20 AM, Edward K. Ream wrote: ​ > > I am presently in the midst of a careful revision of this first comment. >> This is likely the only way that I can understand all the details myself. >> Please review my changes. >> > > ​I have completed the

Re: Matt, what's the status of #562?

On Sat, Jan 27, 2018 at 2:41 AM, Edward K. Ream wrote: I am presently in the midst of a careful revision of this first comment. > This is likely the only way that I can understand all the details myself. > Please review my changes. > ​I have completed the revision. The

Re: Matt, what's the status of #562?

On Fri, Jan 26, 2018 at 12:21 PM, Matt Wilkie wrote: > ... (...just noticed a command mistake, fixing that shortly) >> > > Done. Top post updated and also internal documentation notes with commit > e1eae1f >