Hello,
while I was experimenting with registering handler for idle events,
I have noticed
that there were about 40 registered handlers for idle event. What
was most interesting is the fact that those handlers were all about
the same function onIdle in mod_autosave plugin. At first I thought
that
I've had endless problems with interpreter versioning, leading me to:
class Runwith:
def __init__(self, interpreter, code,
cleanup=True, autorun=True,)
def _prepare_run
def _normalize_code
def run
def _report
def _cleanup
it writes a file to disk, makes it
On Fri, Feb 4, 2011 at 6:58 AM, vitalije vitali...@gmail.com wrote:
Finally, I realized that every time when I invoke unit test command Alt
+5, number of registered handlers increased.
Thanks for this. I'll investigate.
Edward
--
You received this message because you are subscribed to the
On Thu, Feb 3, 2011 at 4:41 PM, Ville M. Vainio vivai...@gmail.com wrote:
- What if you scanned up the tree when pressing ctrl+b, and if one
ancestor had @prelude in it, it would be evaluated as part of the
script, before the code in current node?
Possible. But this could be called a
On Thu, Feb 3, 2011 at 11:45 AM, tfer tfethers...@aol.com wrote:
Normal mode is more interesting.
[big snip]
What I'm saying here is that the problem is more one of developing the
parsing function than binding keys to functions.
Thanks for this. I knew that bindings were not the important
On Fri, Feb 4, 2011 at 8:58 AM, Edward K. Ream edream...@gmail.com wrote:
Do you have any links to discussions of the internals of vim's command
parser? Clearly, it can be duplicated in python ;-)
I have the sources of vim72. It appears that normal.c and ops.c are
where the action is.
I'll
On Fri, Feb 4, 2011 at 4:54 PM, Edward K. Ream edream...@gmail.com wrote:
- What if you scanned up the tree when pressing ctrl+b, and if one
ancestor had @prelude in it, it would be evaluated as part of the
script, before the code in current node?
Possible. But this could be called a
On Fri, Feb 4, 2011 at 9:06 AM, Ville M. Vainio vivai...@gmail.com wrote:
In my books, if a feature is not available by default or just by enabling a
plugin, it doesn't exist)
Interesting rule of thumb. Otoh, exec(g.findTestScript,...) exists by default.
Edward
--
You received this
On Fri, Feb 4, 2011 at 6:04 PM, Edward K. Ream edream...@gmail.com wrote:
In my books, if a feature is not available by default or just by enabling a
plugin, it doesn't exist)
Interesting rule of thumb. Otoh, exec(g.findTestScript,...) exists by
default.
Indeed. I wonder if we could
