Fixed at rev 3ee6afd. Let me know if you find any further problems.
I must admit it seemed to me that this bug was fixed, but here is another
example that demonstrate error in goto-global-line.
In attached Leo file I just put one organizer node and goto-global-line can
not find any
Thanks for the clarification!
Did you try this on Leo itself, having some hundreds of thousands of lines
in one Leo file?
No, because we aren't going to use @clean for Leo.
I tried it on a significant project: pylint. Loading a single .leo is
fast, regardless of size. I
This is why @auto will always be important.
@clean doesn't replace @auto, it's a different set of features
with cost and benefit.
On Tue, Feb 24, 2015 at 5:48 AM, reinhard.engel...@googlemail.com wrote:
Thanks for the clarification!
Did you try this on Leo itself, having some hundreds of
I edited outside Leo for the first time, was surprised to see the
Recovered Nodes tree.
Is this generated any time edits are made on @nosent
outside Leo?
I take it to be strictly informational, the content of the
@nosent tree will always track the external file ... ?
An aside, another
On Tue, Feb 24, 2015 at 5:48 AM, reinhard.engel...@googlemail.com wrote:
Did you try this on Leo itself, having some hundreds of thousands of lines
in one Leo file?
No, because we aren't going to use @clean for Leo.
I tried it on a significant project: pylint. Loading a single
On Tue, Feb 24, 2015 at 5:56 AM, Kent Tenney kten...@gmail.com wrote:
@clean doesn't replace @auto, it's a different set of features
with cost and benefit.
There are no benefits to @auto unless
you are using one of the hyphenated
flavors of @auto: @auto-rst, @auto-vimoutline or
On Tue, Feb 24, 2015 at 5:52 AM, Kent Tenney kten...@gmail.com wrote:
I edited outside Leo for the first time, was surprised to see the
Recovered Nodes tree.
Is this generated any time edits are made on @nosent
outside Leo?
Yes.
I take it to be strictly informational, the content of
