Re: How did I came across Leo?

On Fri, Feb 23, 2018 at 11:35 AM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: > I came about Leo because I was interested in Learning Python and some > forum said that Leo, not Zope, was a superb showcase for this language and > then I found that it supported a form of literate

Re: Should daily snapshots be based on master, devel or both?

On Fri, Mar 2, 2018 at 9:22 PM, Matt Wilkie wrote: Daily snapshots base on devel would be more useful, imo. >> > > I don't know that snapshots are needed at all > ​. > ​I'm not sure either, but I think some people do/did use them.​ > Github allows downloading at will, ex: >

Re: Leo as backbone for dictionary reference service

On Fri, Mar 2, 2018 at 9:15 PM, Matt Wilkie wrote: > > #771 Support --outline-only command-line argument >> is a new issue >> that would skip this pass entirely. >> >> I shall do this only if you actually need it. >> > > I

Re: Terry, please update leo_edit_pane branch in branches.md

On Fri, Mar 2, 2018 at 7:44 PM, Terry Brown wrote: leo_edit_pane was merged into master (and hence devel) some time ago > for more exposure / testing. It does *almost* nothing to core, if you > don't enable the plugin, and even with the plugin enabled, is basically >

Re: For devs: commit only to devel, except maybe branches.md

On Fri, Mar 2, 2018 at 9:27 PM, Matt Wilkie wrote: ​​ Generally speaking I should usually be the only one committing to master. >> And that should happen only when merging a release branch into master. >> > ​Vitalije and I agree that there are reasons for committing to master.

Re: For devs: commit only to devel, except maybe branches.md

On Fri, Mar 2, 2018 at 8:19 PM, vitalije wrote: ​> ​ What about fixing bugs? Should they also go to devel? ​Heh. I was just going to write about this. Reminds me of this joke: ​​ In theory, theory and practice are the same thing. In practice they're different. ​> ​ I

Re: The first, urgent task: show people what Leo already has

If you haven't done so already, you might want to study the user interface of PyCharm (https://www.jetbrains.com/pycharm/), especially their wording of menu entries and their 'Tools' menu. Leo's menu entries are way too much developer-oriented. They express, what's available, not what can be

Re: How did I came across Leo?

I employed Leo for an oddball use case, which it addressed beautifully. How long ago did this start, perhaps 2005? The job that I held then required that, without help from work infrastructure or from colleagues, I write tools for diagnosing and repairing problems with installations of a

Re: For devs: commit only to devel, except maybe branches.md

> Generally speaking I should usually be the only one committing to master. > And that should happen only when merging a release branch into master. > https://github.com/leo-editor/leo-editor/settings/branches has settings for specifying the default branch and marking branches as protected

Re: The first, urgent task: show people what Leo already has

A recent discussion by Terry of the valuespace plugin helped me grasp just one basic idea of what it did. Terry noted "The vs-eval-block command from the valuespace plugin gives Leo a cell like behavior." This seems to be hinting that these cells are similar to the Jupyter cells. If this is

Re: Should daily snapshots be based on master, devel or both?

> > Daily snapshots base on devel would be more useful, imo. > I don't know that snapshots are needed at all. Github allows downloading at will, ex: wget https://github.com/leo-editor/leo-editor/archive/devel.zip pip install https://github.com/leo-editor/leo-editor/archive/devel.zip Same

Re: Leo as backbone for dictionary reference service

> #771 Support --outline-only command-line argument > is a new issue that > would skip this pass entirely. > > I shall do this only if you actually need it. > I don't need it, not right now. I have my hands full with other things. Mostly

Re: For devs: commit only to devel, except maybe branches.md

What about fixing bugs? Should they also go to devel? I have committed recently a fix for the bug that nobody has reported yet, but which has caused me some data loss. On Saturday, March 3, 2018 at 12:34:24 AM UTC+1, Edward K. Ream wrote: > > Generally speaking I should usually be the only one

Re: Terry, please update leo_edit_pane branch in branches.md

On Fri, 2 Mar 2018 15:38:57 -0800 (PST) "Edward K. Ream" wrote: > We both have discussed this branch recently. I'd like to know as > much about it as possible. > > branches.md is the natural place for these docs. They can contain > links more lengthy discussions if you

Re: 2018 will be a momentous year for Leo

It has *already *been a momentous year: - We have a great new git workflow. See branches.md for details. This picture summarizes the idea. - #770

Terry, please update leo_edit_pane branch in branches.md

We both have discussed this branch recently. I'd like to know as much about it as possible. branches.md is the natural place for these docs. They can contain links more lengthy discussions if you like. Edward -- You received this message because you are subscribed to the Google Groups

Should daily snapshots be based on master, devel or both?

Daily snapshots based on master will be less useful now that master is assumed to change slowly. Daily snapshots base on devel would be more useful, imo. Should we offer both? What needs to change to make this happen? Edward -- You received this message because you are subscribed to the

For devs: commit only to devel, except maybe branches.md

Generally speaking I should usually be the only one committing to master. And that should happen only when merging a release branch into master. However, committing branches.md in master is harmless. You can then merge master into devel. *Not the other way!*Edward -- You received this

Re: Leo as backbone for dictionary reference service

On Friday, March 2, 2018 at 2:20:46 AM UTC-6, Edward K. Ream wrote: > On Thu, Mar 1, 2018 at 4:21 PM, Matt Wilkie wrote: > > ​What's the practical limit for number of nodes in Leo? > 3. Leo scans the outline after loading it, looking for @ nodes. This code skips @ignore

Re: The first, urgent task: show people what Leo already has

On Fri, Mar 2, 2018 at 4:40 PM, Satish Goda wrote: > > I totally agree with your observation and a through overview of Leo is in > order to really sell it in an unified way. > > Following are my thoughts on making this happen > > 1. Create a document or presentation

Re: The first, urgent task: show people what Leo already has

Hi Edward. I totally agree with your observation and a through overview of Leo is in order to really sell it in an unified way. Following are my thoughts on making this happen 1. Create a document or presentation called "The Essence of Leo" or "Leo at a Glance" (For presentation

Re: Arguments passed to commands?

On Fri, Mar 2, 2018 at 11:20 AM, Kent Tenney wrote: > More than once I've wished I could put arguments > after the command name, within the command they would > be available as something like *args > ​Please file an enhancement request. This would be useful, but not easy to

Re: is there any particular reason why Leo wouldn't use native QTreeWidget

On Fri, Mar 2, 2018 at 8:02 AM, vitalije wrote: Also speaking about "rendering" tree and how it is expensive has always > seemed a bit strange to me, because I was expecting that rendering tree > items should do QTreeWidget by itself. I've always thought that this >

Arguments passed to commands?

More than once I've wished I could put arguments after the command name, within the command they would be available as something like *args Currently I've got buttons which invoke g.app.gui.runAskOkCancelStringDialog to allow input, but it's somewhat cumbersome. Is there a better way? Thanks,

The first, urgent task: show people what Leo already has

Leo probably *already has* the features you want. Alas, these features can be hidden from casual sight. This is driving me crazy :-) My top priority is to make it obvious to everyone, newbies and devs alike, what Leo can do. Happily, this is a *much easier* task than some of the grand

Re: is there any particular reason why Leo wouldn't use native QTreeWidget

I agree that QTreeView would be better choice. Especially hoisting feature is asking for a QTreeView/Model pair. After all hoisting is just another view into the same model. In current version computed icons are handled by QTreeWidgetItem, so there should be no difference between how it is

Re: is there any particular reason why Leo wouldn't use native QTreeWidget

On Fri, 2 Mar 2018 09:37:22 -0600 Terry Brown wrote: > Not separate from the "let the widget do the rendering" part, don't > forget the dynamic icon generation part Or hoisting, that needs to be supported too. -- You received this message because you are subscribed to

Re: is there any particular reason why Leo wouldn't use native QTreeWidget

On Fri, 2 Mar 2018 06:04:50 -0800 (PST) vitalije wrote: > Just to be clear. I know that Leo uses QTreeWidget for rendering the > tree, but my question is why we don't let it to mange rendering > process all by itself. Separate from the "let the widget do the rendering"

Re: is there any particular reason why Leo wouldn't use native QTreeWidget

Just to be clear. I know that Leo uses QTreeWidget for rendering the tree, but my question is why we don't let it to mange rendering process all by itself. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

is there any particular reason why Leo wouldn't use native QTreeWidget

In another thread Edward wrote: 4. Leo's tree drawing code would likely choke on showing more than a few > thousand nodes. It wasn't the first time that I read about it. Also speaking about "rendering" tree and how it is

Re: Leo 5.7 final released

Thanks! This lowers the hurdle to try leo a little bit. > > -- 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

Re: Rethinking Leo's distribution process

On Thu, Mar 1, 2018 at 2:17 PM, Offray Vladimir Luna Cárdenas < off...@riseup.net> wrote: ​​ > an update menu that uses pip (or conda-anaconda) to let the users be one > click away of the latest version of Leo is important, taking advantage of > having already Leo/Python installed and runnable. >

Re: Leo 5.7 final released

On Fri, Mar 2, 2018 at 4:37 AM, rengel wrote: *Installation*.. > > pip install leo > > *Usage* > > Run leo in your terminal to try how it works. > ​Great idea. Done at bc6ad71 in master and merged master into devel. Edward -- You received this message because

Re: Leo 5.7 final released

Indeed, it does, if I know how to get there. Many GitHub packages have very convenient README.md files that are patterned like ... *Installation* ... *Usage* ... Who would be hurt, if you just add: *Installation*.. pip install leo *Usage* Run leo in your terminal to try how it works.

Re: Leo 5.7 final released

On Fri, Mar 2, 2018 at 3:03 AM, 'Karsten Wolf' via leo-editor < leo-editor@googlegroups.com> wrote: > ​Which update are you talking about? 5.7b1 or b2?​ > > 5.7b1 > ​Noted #757. Thanks. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group.

Re: Leo 5.7 final released

On Fri, Mar 2, 2018 at 2:36 AM, rengel wrote: > 'pip install leo' now works fine. > > What's missing in the 'README.md' on GitHub is a short note on how to > start Leo, > after it has been installed with pip > ​I think this page

Re: Leo 5.7 final released

... > ​Which update are you talking about? 5.7b1 or b2?​ 5.7b1 Now on 5.8 devel ... > ​A search for "tip" in leoSettings.leo will show you: > >@bool show-tips = True​ Fixed and gone. Thanks. -karsten -- You received this message because you are subscribed to the Google Groups

Re: Leo 5.7 final released

'pip install leo' now works fine. What's missing in the 'README.md' on GitHub is a short note on how to start Leo, after it has been installed with pip -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: Leo 5.7 final released

On Fri, Mar 2, 2018 at 12:31 AM, 'Karsten Wolf' via leo-editor < leo-editor@googlegroups.com> wrote: ​[5.7 final] seems to work on OSX. > > Two minor issues which both started with the previous update a few weeks > ago: > ​Which update are you talking about? 5.7b1 or b2?​ - searching and

Re: Leo as backbone for dictionary reference service

On Thu, Mar 1, 2018 at 4:21 PM, Matt Wilkie wrote: ​> ​ What's the practical limit for number of nodes in Leo? ​Good question. I don't know the answer in all its details, but here are a few ideas: 1. Leo now supports representing outlines as sqlite databases, with .leo.db