Re: Why nits matter

On Wed, Feb 14, 2018 at 4:52 AM, Edward K. Ream wrote: ​> ​ I have just created #721 . It will add support for @bool select-next-after-delete setting, with a default that will retain legacy operation. ​> ​ As I write

Please hold all commits to master until 5.7 final

Expect 5.7 final on Friday. I'll be working on documentation and distribution issues until then. Edward -- 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: Why nits matter

On Tue, Feb 13, 2018 at 11:40 AM, Chris George wrote: I have a nit. :-) > > When deleting nodes in the tree, after hitting delete the selection moves > up the tree. When deleting multiple children, this is unintuitive. It would > be better for the selection to move down to

Re: 1d3e6bc: The CompareLeoOutlines class for comparing .leo files

On Tue, Feb 13, 2018 at 6:03 PM, lewis wrote: Please don't delay for me, I'm tied up with work. > ​Rev e172a45 adds the diff-and-open-leo-files command. The diff_leo_files_helper function does all the work for this command and the diff-leo-files commands. Edward --

Re: OTish: asm.js - an extraordinarily optimizable, low-level subset of JavaScript

On Wed, Feb 14, 2018 at 7:27 AM, jkn wrote: > Just for general interest and 'wow'-ness really, given the recent chat > about Node.js, browser integration, ect. ect. > > http://asmjs.org/ > > http://kripken.github.io/mloc_emscripten_talk/ > ​Thanks for the links. Given

Re: OTish: asm.js - an extraordinarily optimizable, low-level subset of JavaScript

That's not all. If you want to see some really neat things check out Web Assembly, the evolution of ASM.js which compiles to a binary and already has support in a few browsers and LLVM. Jacob. On Wed, Feb 14, 2018, 08:22 Edward K. Ream wrote: > On Wed, Feb 14, 2018 at 7:27

Leo 5.7 is code complete. Please test

I plan no further programming work before Leo 5.7 final. Naturally, I'll fix any newly reported serious bugs. Edward -- 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

Re: OTish: asm.js - an extraordinarily optimizable, low-level subset of JavaScript

Hi, Just got this link today: https://webassembly.studio/ ... if you want to play with C or Rust -> WebAssembly :) -m -- 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

Re: (Newbie?) question about js syntax in store/index.js

On Wed, 14 Feb 2018 13:12:10 -0800 (PST) "Edward K. Ream" wrote: > These look kinda like function definitions without "function" or "=>". New to me, but they do seem to be function definitions without function or => Typing in the Chrome console: a = { TEST (x) {

(Newbie?) question about js syntax in store/index.js

I have begun studying LeoVue. I have run across mystifying javascript syntax that googling does not resolve. Any explanation would be welcome. leovue/src/store/index.js contains the Vue store . For study I have refactored this as follows: // =

Re: (Newbie?) question about js syntax in store/index.js

On Wed, Feb 14, 2018 at 3:26 PM, Terry Brown wrote: > On Wed, 14 Feb 2018 13:12:10 -0800 (PST) > "Edward K. Ream" wrote: > > > These look kinda like function definitions without "function" or "=>". > > New to me, but they do seem to be function

Re: (Newbie?) question about js syntax in store/index.js

On Wed, Feb 14, 2018 at 5:03 PM, Edward K. Ream wrote: > > > >> Typing in the Chrome console: >> >> a = >> ​​ >> { TEST (x) { return(x+2) } } >> a.TEST(2) >> 4 >> > ​So these two lines are equivalent: ​ { TEST (x) { return(x+2) } } ​ { TEST: function (x) { return(x+2) } }

Re: (Newbie?) question about js syntax in store/index.js

On Wed, 14 Feb 2018 17:26:10 -0600 "Edward K. Ream" wrote: > ​So these two lines are equivalent: > > ​ > { TEST (x) { return(x+2) } } > ​ > { TEST: function (x) { return(x+2) } } > > Edward http://www.benmvp.com/learning-es6-enhanced-object-literals/ explains a bit more