Re: My last lecture. Part 1: Why Leo is noteworthy

Aha! It's good to hear this praise from a fellow Ecco user. It gives me some confidence that the investment will be well repaid. Rob, do you have any advice for someone following in your footsteps? (If this isn't appropriate for this group, write me offline: don, of the domain dondwiggins

Possible pylint/goto-global-line bug and lost in Leo's internals

I've gotten quite lost quite fast while trying to track down a possible bug with pylint and goto-global-line. I can't figure out which is the culprit and I'm struggling to make my way through Leo's source to track it down. I've included my leo file which has a test file in it. After having the

Re: My last lecture. Part 1: Why Leo is noteworthy

Well, I wouldn't go as far as Marcel, but there is a tension here between brevity and general comprehensibility. Ed, you've lived and breathed Leo for years, so those particular single letter names are probably etched in your neural circuitry. Others, however, might have more difficulty

Re: My last lecture. Part 1: Why Leo is noteworthy

On Thu, 5 Nov 2015 09:50:32 -0800 Don Dwiggins wrote: > Well, I wouldn't go as far as Marcel, but there is a tension here > between brevity and general comprehensibility. Ed, you've lived and > breathed Leo for years, so those particular single letter names are >

Re: Possible pylint/goto-global-line bug and lost in Leo's internals

Well I figured part of it out, gotoCommands.py is missing from LeoPyRef.leo in core classes --> command classes. I would make the change to this myself but after I make the changes to LeoPyRef.leo my nodes are starting to look funny in the .leo file, for example this: @file

Re: Possible pylint/goto-global-line bug and lost in Leo's internals

Did I absolutely completely forget to include my example .leo file!? Any, it's NOW included. On Thursday, November 5, 2015 at 1:01:15 PM UTC-5, john lunzer wrote: > > Well I figured part of it out, gotoCommands.py is missing from > LeoPyRef.leo in core classes --> command classes. > > I would

ECCO refugees?

To Don (and others who have already migrated or are considering migrating to Leo from ECCO Pro): ECCO Pro was a terrific program back in the '90s that allowed for multiple views of the same data in an outline-centric display with most of the capabilities of a PIM. Unfortunately, the developers

Re: Possible pylint/goto-global-line bug and lost in Leo's internals

On Thu, 5 Nov 2015 10:01:15 -0800 (PST) john lunzer wrote: > Well I figured part of it out, gotoCommands.py is missing from > LeoPyRef.leo in core classes --> command classes. > > I would make the change to this myself but after I make the changes > to LeoPyRef.leo my nodes

Re: Session doesn't recognize mapped network locations on restore

Haven't seen any replies so I'm wondering if I should post this as a bug? Rob.. -- 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: Session doesn't recognize mapped network locations on restore

On Thu, 5 Nov 2015 17:38:10 -0800 (PST) Largo84 wrote: > Haven't seen any replies so I'm wondering if I should post this as a > bug? > > Rob.. I think it would make sense to add it to the bug tracker. I vaguely remember a discussion about this long ago. Wonder if