Re: Looking over my should while I add support for jedi autocompletion

On Wednesday, May 16, 2018 at 10:21:00 AM UTC-5, Edward K. Ream wrote: > > Chris George said he would like to look over my shoulder while I do #309: Add > support for Jedi autocompletion. > > The comments in #309 now show how I developed the

Re: Looking over my should while I add support for jedi autocompletion

On Thursday, May 17, 2018 at 5:11:32 AM UTC-5, Edward K. Ream wrote: The last comment shows @button jedi, which does everything except actually > calling jedi to get the completions. > The node's local line number (and corresponding line) must be reconciled exactly with the global sources

Away until Monday

Rebecca and I are traveling to Seattle later today to attend our daughter Linda's wedding :-) I'll have my laptop with me for emergencies, but I expect none. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group

Re: Looking over my should while I add support for jedi autocompletion

On Thursday, May 17, 2018 at 5:59:17 AM UTC-5, Edward K. Ream wrote: The node's local line number (and corresponding line) must be reconciled > exactly with the global sources returned by > goto.get_external_file_with_sentinels. > Experiment 6

Re: Documentation on new data model for Leo outlines

> > I have just published first two articles about what I have done so far in > this mini-project. Here are the links: > [...] > All comments are welcome. > Vitalije, I'm working my through your posts on that site from the beginning. It's slow because I understand little because of my

Re: Documentation on new data model for Leo outlines

On Thu, 17 May 2018 12:00:30 -0700 (PDT) Matt Wilkie wrote: > > Veering off topic I wish there was a more general solution for dot > > access to dict members, I understand all the arguments against, but > > often writing mathematical expressions... > > > > col = (pos['x'] -

Re: Documentation on new data model for Leo outlines

the rest of this thread is over my head, but: Veering off topic I wish there was a more general solution for dot > access to dict members, I understand all the arguments against, but > often writing mathematical expressions... > > col = (pos['x'] - grid['minx']) / (grid['maxx'] - grid['minx'])

Re: Documentation on new data model for Leo outlines

> > > > col = (pos.x - grid.minx) / (grid.maxx - grid.minx) * grid.cols > > > > > +10! > > Given the +10 :) I should add I've been using this lib.: > > https://pypi.org/project/addict/#description > Thanks! -- You received this message because you are subscribed to the Google Groups