Hello!
I have recently noticed strange behaviour of testing in Leo. Somehow tests
run ok, but they are still reported as broken.
Even a node with headline '@test example' and body of just one line 'assert
True' is reported as FAILD
Here is traceback:
File
I don't see a point in doing that in a subclass, since you only need
to hash so rarely.
On Fri, Oct 14, 2011 at 11:44 PM, Edward K. Ream edream...@gmail.com wrote:
On Fri, Oct 14, 2011 at 2:18 PM, Ville M. Vainio vivai...@gmail.com wrote:
Better use id (it) instead of just 'it' then
Ah. I
On Fri, Oct 14, 2011 at 4:06 PM, Terry Brown terry_n_br...@yahoo.com wrote:
On Fri, 14 Oct 2011 13:52:48 -0700 (PDT)
SegundoBob bhoss...@ieee.org wrote:
Great idea. I played with the save tabs button you suggest, and I
noticed that the start up messages to the Log Pane get messed up.
When I
On Sat, Oct 15, 2011 at 3:10 AM, Ville M. Vainio vivai...@gmail.com wrote:
I don't see a point in doing that in a subclass, since you only need
to hash so rarely.
Thanks for your comments. They have kept alive a hidden question.
The timing is interesting. I am now in possession of a .leo
The more I think about it, the more Kent's response:
Dingdingding! That's the prizel.
to the question::
Wouldn't it be great if we all could remember what we,
and others, have already done :-)
points the way to some great new features of Leo. Maybe even a
unifying, simplifying
On Sat, Oct 15, 2011 at 1:22 AM, vitalije vitali...@gmail.com wrote:
I have recently noticed strange behaviour of testing in Leo. Somehow tests
run ok, but they are still reported as broken.
Even a node with headline '@test example' and body of just one line 'assert
True' is reported as FAILD
On Sat, 15 Oct 2011 06:45:30 -0500
Kent Tenney kten...@gmail.com wrote:
Dang. That also makes it hard to save the current position, an important
aspect.
Sounds like Leo needs a commander container.
instead of
g.openWithFileName('/home/ktenney/work/explanans.leo', c)
I think, off the top
A dict like this is the wrong place to keep widgets alive. Widgets belong to
other objects, probably the container they reside in. The mission of this dict
is to trigger an action when a widget has been clicked. A widget that does not
exist anymore can't be clicked in the first place, a widget
I do test externally all the time and haven't noticed the above problem
until recently.
Anyway, thanks for the fix.
PS: I don't think that assert True need any gui related function as many
other tests. In fact I use a lot of tests just to execute some code without
writing script file and then
On Sat, Oct 15, 2011 at 1:06 PM, vitalije vitali...@gmail.com wrote:
I do test externally all the time and haven't noticed the above problem
until recently.
The problems stem from newly enabled plugins.
Edward
--
You received this message because you are subscribed to the Google Groups
On Oct 15, 12:36 pm, vivai...@gmail.com wrote:
A dict like this is the wrong place to keep widgets alive. Widgets belong to
other objects, probably the container they reside in. The mission of this
dict is to trigger an action when a widget has been clicked. A widget that
does not exist
On Fri, Oct 14, 2011 at 4:06 PM, Terry Brown terry_n_br...@yahoo.com wrote:
I think it's a major thing to fix though. Basically Leo has no concept
of the current commander.
There are at least two separate issues here.
1. g.app.setLog and c.setLog.
As usual when switching between contexts,
Did I cause appearing of this problem with enabling a new plug-in previously
disabled? (I really did change @enabled plug-ins setting recently)
I would prefer if it would be possible to launch tests externally without
loading plug-ins.
As I see in Code--Testing--@file
On Sat, Oct 15, 2011 at 12:01 AM, lewis lewisn...@operamail.com wrote:
In build 4591 get this traceback from HelpApropos Debugging Commands:
File C:\Python32\Lib\site-packages\leo-editor\leo\core
\leoPlugins.py, line 550, in loadOnePlugin
toplevel = __import__(moduleName)
ImportError:
On Sat, Oct 15, 2011 at 3:54 PM, vitalije vitali...@gmail.com wrote:
Did I cause appearing of this problem with enabling a new plug-in previously
disabled? (I really did change @enabled plug-ins setting recently)
You might have caused the problem in some sense, but in a truer
sense you had
If I understand your vision for this, it sounds intriguing. It would
certainly help my own workflow as I'm now working with numerous .leo
files scattered everywhere. A cross-file clone (or pseudo-clone) or
even a node that can be updated at will from a template would all be
very beneficial, and
On Sat, Oct 15, 2011 at 5:03 PM, Edward K. Ream edream...@gmail.com wrote:
I am not sure what happens at present, and I'm not sure whether any settings
apply to these commands.
Good news (mostly): you can set up dynamic unit tests exactly the way you want.
I was going to point you at the
On Oct 15, 9:29 am, Edward K. Ream edream...@gmail.com wrote:
Wouldn't it be great if we all could remember what we,
and others, have already done :-)
As one small step in this direction, rev 4597 changes the
mod_scripting plugin so that the name of the command created by an
@button
18 matches
Mail list logo
