Re: Rethinking Leo's distribution process

Hello Edward, 2018-02-28 17:05 GMT+01:00 Edward K. Ream : > On Wednesday, February 28, 2018 at 9:59:02 AM UTC-6, Edward K. Ream wrote: > > I am not satisfied with the profit/effort ratio. Here are preliminary >> thoughts. >> > > I would like to release "lite" versions of Leo

a74f9a0e: #748: much improved print-settings command

Leo's print-setting command is now a joy to behold: - Added explanation of "@" in legend. - Added type of setting `@data`, `@string`, etc. Why was this never done before?? - Much improved formatting of `@data` nodes containing fewer than 20 non-comment lines. It is amazing how useful this

Re: Leo 5.7 final released

> ​As I understand it, Matt will have to create a new wheel. Right? Or is > this something that I am supposed to do? > Done, just a few moments ago. In process discovered and fixed a bug in setup.py (long description left out), but i won't have time to commit that until tomorrow. matt --

Re: Jupyter as Leo's what ? [via] A study outline containing eric6 docs

> > +1. This is why I tend to use Pyzo when prototyping new python code. >> > > ​Pyzo has an integrated console window. Is this what you are talking > about?​ > > Is the Stupendous Aha > > > not convenient

leovue meets leo4sqlite

The script 'leo4sqlite' is now online using leovue - the syntax highlighting works well. I'm looking forward to trying some of leovue's more advanced capabilities. My leovue/leo4sqlite demo lives here: https://tscv11.github.io/leo4sqlite/#/t/23/ tscv11 -- You received this message because

Re: leovue meets leo4sqlite

On Wed, 28 Feb 2018 13:26:43 -0800 (PST) tscv11 wrote: > The script 'leo4sqlite' is now online using leovue - the syntax > highlighting works well. > I'm looking forward to trying some of leovue's more advanced > capabilities. > > My leovue/leo4sqlite demo lives here: >

Re: Joe, building LeoVue fails for me on Windows and Ubuntu

Oops.. thought I had removed xst4node and xmldom from package.json. Those require java, and that could be an issue for Windows. I just removed those and tried an install on a new Windows installation and was able to get npm install to work with no problems. The xslt4node and xmldom packages

Re: Joe, building LeoVue fails for me on Windows and Ubuntu

I have been using Leo and Nikola to write, build and deploy a static site. Nikola is written in python, so it was little more familiar to me than setting up a Ruby environment. Chris On Wednesday, February 28, 2018 at 5:38:39 PM UTC-8, Joe Orr wrote: > > Oops.. thought I had removed xst4node

Re: pytest integration for Leo

On Wed, 28 Feb 2018 08:06:48 -0600 "Edward K. Ream" wrote: > On Tue, Feb 27, 2018 at 3:45 PM, Terry Brown > wrote: > > > For anyone using the pytest framework I've written a button which > > jumps between code and corresponding test, creating missing

Re: pytest integration for Leo

On Tue, Feb 27, 2018 at 3:45 PM, Terry Brown wrote: > For anyone using the pytest framework I've written a button which jumps > between code and corresponding test, creating missing folders / files / > functions as needed. It's doc'ed in it's doc string. > >

Re: Improvements in reading external files

I should have mentioned that this is my first code ever written in Rust. More experienced Rust programmers will probably find that it is not very idiomatic. I will try to improve it as I learn more about Rust. Vitalije -- You received this message because you are subscribed to the Google

Re: Jupyter as Leo's what ? [via] A study outline containing eric6 docs

On Sun, Feb 25, 2018 at 8:57 AM, Zoom.Quiet wrote: Hummm.. IMHO: > - theme is important for developer > - but easy switch theme is not big things > - because if someone always switch theme for show > must one designer not developer, > when i config love theme, never

Re: Jupyter as Leo's what ? [via] A study outline containing eric6 docs

On Tue, Feb 27, 2018 at 3:36 PM, Matt Wilkie wrote: > > BUT: >> Leo can not like IDE/Jupyter can running on the spot, >> and every one time change interface, >> such as leave Leo, jump into iTerm2 for running code , observe log >> printing, >> will hurt attention, lost Mind

Re: Improvements in reading external files

Next on my todo list is to implement in Rust one of the following two: 1. new data model for Leo tree 2. javascript parser using rust library for parsing modern javascript and exporting to python extension module About 1: I had this idea and had made some experiments last summer, and

Re: pytest integration for Leo

:-] Important distinction. On Wed, Feb 28, 2018 at 8:18 AM, Terry Brown wrote: > On Wed, 28 Feb 2018 08:06:48 -0600 > "Edward K. Ream" wrote: > > > On Tue, Feb 27, 2018 at 3:45 PM, Terry Brown > > wrote: > > > > > For anyone

live update of abbreviations

This may not be feasible, I don't know the implementation. I've rediscovered the power of abbreviations, and working on some fairly involved ones, I check my work often. I seem to recall a time when doing a followed by would apply @settings changes, but now it seems the file must be closed and

Re: Merging 5.8-dev into master is next

Although the Leo way is working, it might be advantageous to adopt what has become standard, making potential contributers more comfortable: working on a develop branch instead of master. Along these lines, issuing pull requests instead of pushing is a good way for changes to be vetted. I was

Re: Rethinking Leo's distribution process

On Wednesday, February 28, 2018 at 9:59:02 AM UTC-6, Edward K. Ream wrote: I am not satisfied with the profit/effort ratio. Here are preliminary > thoughts. > I would like to release "lite" versions of Leo every month or so. These would appear only on PyPI and github. Nothing on sourceforge.

Re: Merging 5.8-dev into master is next

On Wed, Feb 28, 2018 at 9:34 AM, Kent Tenney wrote: > Although the Leo way is working, it might be advantageous to > adopt what has become standard, making potential contributors > more comfortable: working on a develop branch instead of master. > > Along these lines, issuing

Rethinking Leo's distribution process

After a week working on 5.7 final, I am not at all satisfied with the profit/effort ratio. Here are preliminary thoughts. Your comments are welcome. Now that `pip install leo` is feasible, I believe we can emulate Jupyter's install page .

Re: Leo 5.7 final released

On Wed, Feb 28, 2018 at 3:34 AM, rengel wrote: > pip installs leo-5.7b2.dev27-py2.py3-none-any.whl > > Doesn't look like the final version. > ​As I understand it, Matt will have to create a new wheel. Right? Or is this something that I am supposed to do? Edward

Re: Add branch.md to .gitignore?

On Tue, Feb 27, 2018 at 3:39 PM, Matt Wilkie wrote: > > Adding branch.md to .gitignore would allow branch devs to document their >> branch-specific work, without the possibility of overwriting this file when >> merging (in either direction). >> > > name-of-branch.md ? >

Re: Merging 5.8-dev into master is next

On Tue, Feb 27, 2018 at 3:41 PM, Terry Brown wrote: I think with the release branch approach master is the place for > finished projects being tested, sort of what it is now, it's just that > instead of people having to switch between "ok to use master" and "not > ok to use master", it's always

Re: Leo 5.7 final released

pip installs leo-5.7b2.dev27-py2.py3-none-any.whl Doesn't look like the final version. -- 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

Re: Merging 5.8-dev into master is next

Am Dienstag, 27. Februar 2018 21:36:11 UTC+1 schrieb Edward K. Ream: > > On Tue, Feb 27, 2018 at 2:19 PM, Matt Wilkie > wrote: > > Would it be easier to invert the process, and have dedicated releases >> branches and then master never needs to be frozen? >> > > ​Anything is

Re: Joe, building LeoVue fails for me on Windows and Ubuntu

On Wed, Feb 28, 2018 at 4:46 AM, Joe Orr wrote: Sorry, was offline for a week. Still having problems? > ​I was able to build and run leovue on Ubuntu only.​ ​The info item #735: Installing and running LeoVue contains

Re: live update of abbreviations

On Wed, Feb 28, 2018 at 10:00 AM, Kent Tenney wrote: I seem to recall a time when doing a followed by > would apply @settings changes, but > now it seems the file must be closed and re-opened. > ​This came up a few days ago, and I didn't follow up on it. Have you tried the

Re: Improvements in reading external files

On Wed, Feb 28, 2018 at 8:44 AM, vitalije wrote: > > v1: average time: 159.9 ms > v2: average time: 44.9 ms > ​ Many thanks for this important work.​ > Yesterday I have re-implemented the above algorithm in Rust. Loading > leoGlobals.py using this Rust extension on my

Re: Rethinking Leo's distribution process

On Wed, 28 Feb 2018 07:59:02 -0800 (PST) "Edward K. Ream" wrote: > - Mark all significant items with the lvl:major label. I added that originally to indicate bug severity - fine with it being re-purposed (although it makes lvl:minor/medium weird), but check and delete uses

Re: live update of abbreviations

On Wed, Feb 28, 2018 at 10:26 AM, Kent Tenney wrote: > Sweet! > > I was looking at the refresh-* commands, > reload-* does the trick. > ​Oh good. Thanks for the confirmation. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor"

Switch to master/devel organization of branches?

Marcel Franke made a strong case for viewing Leo's master branch as inherently stable, using a devel branch as the bleeding edge. He provides this clear picture of the process. The more I think about this,

Re: Improvements in reading external files

On Wed, Feb 28, 2018 at 8:57 AM, vitalije wrote: Next on my todo list is to implement in Rust one of the following two: > >1. new data model for Leo tree >2. javascript parser using rust library for parsing modern javascript >and exporting to python extension

Re: live update of abbreviations

Sweet! I was looking at the refresh-* commands, reload-* does the trick. Thanks, Kent On Wed, Feb 28, 2018 at 10:16 AM, Edward K. Ream wrote: > On Wed, Feb 28, 2018 at 10:00 AM, Kent Tenney wrote: > > I seem to recall a time when doing a followed by

Re: Rethinking Leo's distribution process

On Wed, Feb 28, 2018 at 10:58 AM, Terry Brown wrote: > - Mark all significant items with the lvl:major label. > > I added that originally to indicate bug severity - fine with it being > ​ ​ > re-purposed > ​... > ​I think that lvl:major label can be applied to enhancements as well as bugs

Re: Switch to master/devel organization of branches?

On Wednesday, February 28, 2018 at 11:01:42 AM UTC-6, Edward K. Ream wrote: Marcel Franke made a strong case for viewing Leo's master branch as > inherently stable, using a devel branch as the bleeding edge. He provides > this clear picture >

Re: Merging 5.8-dev into master is next

Am Mittwoch, 28. Februar 2018 11:01:04 UTC+1 schrieb Edward K. Ream: > > On Wed, Feb 28, 2018 at 3:39 AM, 'Marcel Franke' via leo-editor < > leo-e...@googlegroups.com > wrote: > >> >> The usual way to do this today: >> >> master as stable. >> develop as unstable. >> release as pre-stable. >> >>

Re: Joe, building LeoVue fails for me on Windows and Ubuntu

Sorry, was offline for a week. Still having problems? I did a clean install on a new Ubuntu and no problems. Also, it can be run with Docker (there is a Dockerfile now). Joe On Monday, February 19, 2018 at 12:42:11 PM UTC-5, Edward K. Ream wrote: > > > > *Windows*See #735: Installing and

Re: Merging 5.8-dev into master is next

On Wed, Feb 28, 2018 at 4:21 AM, 'Marcel Franke' via leo-editor < leo-editor@googlegroups.com> wrote: It doesn't matter how stable or unstable develop-branch becomes, but master > has to be stable and reliable all the time, always. > ​I can understand why organizations might adopt this point of