Forget the decorator!
I'm not sure what you try to accomplish.
Your publicCommands tables in Leo already associate command_names with
functions or methods, so you don't need a decorator for that. As you told
Terry (somewhere above) you need to retrieve the information if you need a
'self'
`file:///home/tbrown/t/Package/leo/git/leo-editor/leo/plugins/leoPluginsRef.leo#Plugins:2--Scripting:14--@file%20leoscreen.py:0--cmd_run_all_here%20(leoscreen_Controller):12`
and friends are getting ``c`` instead of ``{'c':c}`` now as their first
argument.
Also, ``Ctrl-B`` on:
.. code:: py
On Sun, May 17, 2015 at 4:04 AM, reinhard.engel...@googlemail.com wrote:
Forget the decorator!
:-)
The per-class (per-module) decorators in Leo's code do work, they are
defined before the class to which they apply and the decorators themselves
appear before what *looks *to be a
On Sat, May 16, 2015 at 4:29 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
No PEP 8 transformations should be made without watching this:
https://www.youtube.com/watch?v=wf-BqAjZb8M
Thanks for this link. It's a good talk. As far as gorillas go, c, g and
c.p are
On Sat, May 16, 2015 at 3:58 PM, Edward K. Ream edream...@gmail.com
wrote:
Beautifying, reformatting or otherwise improving code could potentially
change its meaning.
Now that Terry has put the code beautification problem in context, let's
think about solving the original problem. Here
I was about to ask are you sure it's focus? In case 1, where the body text
exactly matches the node text, the text is not found. However in case 2 the
text is found straight away.
But you may be right about the focus :)
Follow case 1, but with an extra step:
1. Open Leo file.
Create a node
On Sunday, May 17, 2015 at 7:00:44 AM UTC-5, Edward K. Ream wrote:
Stylistic *hangnails *weigh on my mind. I wish they didn't, but they do.
Well, this is really the insight behind Getting Things Done.
We want to get things off our minds and into a framework so we don't have
to think about
