Huh?
There's a fair amount of logic in the @root tangle code to allow or
disallow multiple parts to a section definition.
It makes sense that when encountering a section reference (i.e., a
point at which a section is to be interpolated) that you shouldn't at
that point be in the midst of
I've just pushed 3108 to the trunk. Some @root unit tests now work
due to fixes in leGlobals.py and leoTangle.py; some still fail. Much
more to do.
I've included a (failing) unit test with a fanciful interpretation of
what multiple @comment directives should do in a single node. I'd
like to
I'm trying to import a python source code file into leo via Main menu-
File-Import-Import To @file.
For a minimal example consider that the file contains this code:
--- cut here ---
class MyClass:
def method1(self):
pass
m1 = method1()
def method2(self):
pass
On Wed, 2 Jun 2010 05:01:24 -0700 (PDT)
zpcspm zpc...@gmail.com wrote:
As you can see, the line m1 = method1() landed into the second
child.
I think that leo really only sees the def and class blocks, and just punts on
where to put the stuff that comes between them. A @decorator should
On Jun 2, 5:31 pm, Terry Brown terry_n_br...@yahoo.com wrote:
class t(object):
def m1(self):
pass
m = m1
def m2(self, func=m):
print func
I know that's a weird piece of code, but I think you could argue the m = m1
belongs with the m2 definition in that
On Jun 2, 11:31 pm, Terry Brown terry_n_br...@yahoo.com wrote:
Comments are harmless of course, but you still might miss an important comment
for function X if the comment gets shoved into function Y's node.
For the minty case, dumb place to put the comment, no way to tell whether it
applies to
On Thu, 3 Jun 2010 10:05:07 +0800
Zoom.Quiet zoom.qu...@gmail.com wrote:
what happen? and what can i do?
I think you use Read @file nodes.
Perhaps the documentation is out of date.
Cheers -Terry
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
