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

Perhaps there is the answer: {'icons': [{'file': u'C:\\Users\\Lunzer\\Documents\\leo-editor\\leo\\themes\\leo_dark_0\\Icons\\file_icons\\file_file.png', 'on': 'vnode', 'relPath': u'C:\\Users\\Lunzer\\Documents\\leo-editor\\leo\\themes\\leo_dark_0\\Icons\\file_icons\\file_file.png',

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: 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

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