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',
'type': 'file',
'visualIcon': '1',
'where': 'beforeHeadline',
'xoffset': 2,
'xpad': 1,
'yoffset': 0}],
'lineYOffset': 3}
On Thursday, November 5, 2015 at 10:56:30 PM UTC-5, Terry Brown wrote:
>
> On Thu, 5 Nov 2015 10:01:15 -0800 (PST)
> john lunzer <[email protected] <javascript:>> 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 are starting to look funny in the .leo file,
> > for example this:
>
> I've seen that kind of change before. What does g.es(p.v.u) show on
> the changed node, or its decedent? Wondering if it's a particular
> plugin unnecessarily leaving greasy fingerprints on things.
>
> Cheers -Terry
>
> > <v
> > t="ekr.20150514035236.1"><vh>@file
> ../commands/abbrevCommands.py</vh></v>
> >
> > turned into this:
> >
> > <v t="ekr.20150514035236.1"
> >
> descendentVnodeUnknownAttributes="7d710055013071017d7102550b6c696e65594f666673657471034b0073732e"><vh>@file
>
>
> > ../commands/abbrevCommands.py</vh></v>
> >
> > Not sure what to make of that change but I thought I'd verify what
> > that mean before checking it in.
> >
> > On Thursday, November 5, 2015 at 12:42:46 PM UTC-5, john lunzer wrote:
> > >
> > > 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 outline create the file do right click "Run Pylint" and then
> > > get the line number where it complains about "import pudb" and then
> > > use that line number in the goto-global-line command. In my most
> > > recent version of Leo it brings me to three line above the import
> > > line which is exactly the amount of leo directives in that same
> > > node.
> > >
> > > I've gotten lost because in searching through the source code I
> > > appear to be finding calls to functions that don't have definitions
> > > or finding definitions which have no calls. For example I appear
> > > unable to find the definition of c.gotoCommand.find_script_line
> > > using either find-def, quicksearch, or built in find.
> > >
> > > I would appreciate any help on where I've gone wrong!
> > >
> >
>
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
