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

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote: I did all the installs in separate consoles. These consoles tell me > everything except the order in which they were installed ;-) Hmm, maybe I > should add a time stamp to the console prompts... > There's too much cruft

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

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote: > See #735: Installing and running LeoVue Hurray! LeoVue now works properly for me on Ubuntu with Mozilla. #735 presents a summary of what I did. There are some fine

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

On Monday, February 19, 2018 at 11:55:28 AM UTC-6, Kent Tenney wrote: Ubuntu main is too old, use the node repo > This is what I have: > curl -sL https://deb.nodesource.com/setup_6.x | bash - > It turns out that the following is required (gnashes teeth): curl -sL

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

On Monday, February 19, 2018 at 11:55:28 AM UTC-6, Kent Tenney wrote: Ubuntu main is too old, use the node repo > This is what I have: > curl -sL https://deb.nodesource.com/setup_6.x | bash - > > which is a shortcut to add the node repo > > after that > apt-get install nodejs > installs current

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

Ubuntu main is too old, use the node repo This is what I have: curl -sL https://deb.nodesource.com/setup_6.x | bash - which is a shortcut to add the node repo after that apt-get install nodejs installs current version On Mon, Feb 19, 2018 at 11:47 AM, Edward K. Ream wrote:

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

Yes, I would suspect that ancient Node version first and foremost. The NodeJS site has a repository you can add for more up to date versions of their software. On Mon, Feb 19, 2018, 11:47 Edward K. Ream wrote: > On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K.

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

On Monday, February 19, 2018 at 11:42:11 AM UTC-6, Edward K. Ream wrote: It's troubling that the Ubuntu versions are so much lower than corresponding Windows versions. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

Joe, building LeoVue fails for me on Windows and Ubuntu

*Windows*See #735: Installing and running LeoVue *Ubuntu* I have, at one time or another this morning, done the following: Reinstalled node.js sudo apt install default-jdk npm install -g dev-server sudo npm install -g gyp # Seems to

Re: Error starting Leo: 'NoneType' object has no attribute 'QObject'

On Thu, Feb 15, 2018 at 7:32 PM, John Clark wrote: @Edward K Ream: I might suggest that (at least in the near term) some > popular linux distros (including Debian) are shipping systems that contain > both python v2 and python v3 and therefore this issue is probably

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

On Mon, Feb 19, 2018 at 9:33 AM, Zoom.Quiet wrote: > > after test, i confirm: > > - change @rst -> @clean, will lost so many rST need support by Leo > > - and @rst really can not auto merge changed from out files > ​Yes, this is a problem. I don't know of any simple

Re: Scripting leo: Programmatic way to reference the vnode containing the script that is being executed?

On Tuesday, February 20, 2018 at 12:31:38 AM UTC+11, Edward K. Ream wrote: > > > I have just created #736: Predefine script_p and script_gnx values in Leo > scripts , with a 5.8 > milestone. > > You could create your own execute-script

Re: effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

On Sat, Feb 17, 2018 at 11:14 PM, Zoom.Quiet wrote: > 2 years ago: Re: How to collaborate using Leo > https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ > discuss about Leonard(Leo user) and Nancy(not Leo user) how to work together, > the result is : >

A study outline: leovue/dist/static/components.leo

Attached is a *copy* of components.leo. It is for study only. It may be in the dist directory, but it's likely that Joe, not a script, created its contents. I added many new sections to make the overall organization easier. Edward -- You received this message because you are subscribed to

Re: Scripting leo: Programmatic way to reference the vnode containing the script that is being executed?

On Sunday, February 18, 2018 at 11:21:51 PM UTC-6, Edward K. Ream wrote: p is the position of the script for @button nodes, @command nodes and for > scripts executed by Leo's execute-script command.​ > Oops. My brain spike. As you say, p is c.p. I have just created #736: Predefine script_p and

Re: d026066: the leovue command

On Mon, Feb 19, 2018 at 1:49 AM, Edward K. Ream wrote: 2. Build the app: run `npm install` from the > ​[leovue] folder. > This fails for me on Windows, as discussed in #735 > due to problems > installing node-java. >

Re: ENB: Why python will remain Leo's future

On Mon, Feb 19, 2018 at 3:22 AM, jkn wrote: Rust is an interesting language, but it is totally unsuitable for >> non-professional programmers. >> > > I'd be interested in learning more about your views of why this is... > ​Rustaceans must be aware of lifetimes.​ ​

Re: ENB: Why python will remain Leo's future

Hi Edward On Sunday, February 18, 2018 at 9:53:38 PM UTC, Edward K. Ream wrote: > > On Friday, February 16, 2018 at 3:45:23 AM UTC-6, Edward K. Ream wrote: >> >> Rewriting Leo's core is out of the question. Python is: >> >> - Best for users as the simplest and most flexible scripting language. >>