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.
