On Tue, Jul 15, 2014 at 8:17 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
It seems that the uA persisting code really should try and save uA
info on nodes it can't match...
I agree.
I guess it's a question of what the uA data is.
No. It's simply a question of where
On Wednesday, July 16, 2014 2:16:45 AM UTC-5, Edward K. Ream wrote:
On Tue, Jul 15, 2014 at 8:17 PM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
...it may be best simply to require an exact match, and fall back on
creating nodes to hold uA's in case no match is found.
On 7/16/2014 8:59 AM, Edward K. Ream wrote:
the simplest thing that could possibly work
Ockham's Razor at work! Good :)
Nice work, Edward. Keep it up!
--Jake
--
You received this message because you are subscribed to the Google Groups
leo-editor group.
To unsubscribe from this group and
First impressions:
- the @auto node icons indicate they are clones
- I'm not sure why the @persistence tree is visible, can it
be used for something? Maybe somehow useful in resolving
issues?
On Wed, Jul 16, 2014 at 8:29 AM, Jacob Peck gatesph...@gmail.com wrote:
On 7/16/2014 8:59 AM, Edward
On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney kten...@gmail.com wrote:
First impressions:
- the @auto node icons indicate they are clones
Only if they are clones :-)
- I'm not sure why the @persistence tree is visible, can it be used for
something? Maybe somehow useful in resolving issues?
On Wednesday, July 16, 2014 9:14:59 AM UTC-5, Edward K. Ream wrote:
On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney kten...@gmail.com wrote:
First impressions:
- the @auto node icons indicate they are clones
Only if they are clones :-)
I do notice that the icon box has a black
On Wed, Jul 16, 2014 at 9:14 AM, Edward K. Ream edream...@gmail.com wrote:
On Wed, Jul 16, 2014 at 9:00 AM, Kent Tenney kten...@gmail.com wrote:
First impressions:
- the @auto node icons indicate they are clones
Only if they are clones :-)
No, all of them, none are clones. Sounds like
On Wednesday, July 16, 2014 9:22:03 AM UTC-5, Edward K. Ream wrote:
I do notice that the icon box has a black border, indicating that the
@auto node is dirty. That's a recent problem. I'll fix it asap.
This looks like an interaction problem with the bookmarks.py plugin. Not
exactly sure
On Wed, 16 Jul 2014 11:41:37 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
On Wednesday, July 16, 2014 9:22:03 AM UTC-5, Edward K. Ream wrote:
I do notice that the icon box has a black border, indicating that
the
@auto node is dirty. That's a recent problem. I'll fix it
On Wed, Jul 16, 2014 at 9:14 AM, Edward K. Ream edream...@gmail.com wrote:
I just upped code that starts to support @recovery trees in each per-file
@data tree:
Rev 9a082a8... fixes several problems. All tests pass, including some
by-hand tests of real-world scenarios.
The only remaining
On Monday, July 14, 2014 2:00:48 PM UTC-5, Edward K. Ream wrote:
On Mon, Jul 14, 2014 at 11:49 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I asked a vague question about the status of vc.find_absolute_unl_node
and vc.find_position_for_relative_unl the other day,
On Tue, 15 Jul 2014 04:39:06 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
On Monday, July 14, 2014 2:00:48 PM UTC-5, Edward K. Ream wrote:
On Mon, Jul 14, 2014 at 11:49 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I asked a vague question about the
On Tue, Jul 15, 2014 at 7:04 AM, 'Terry Brown' via leo-editor
It seems that the uA persisting code really should try and save uA info on
nodes it can't match...
So what I was thinking was that the orphan nodes could have an UNL (in
their uAs :-) which points to the best guess imported node,
On Tue, 15 Jul 2014 17:50:21 -0500
Edward K. Ream edream...@gmail.com wrote:
On Tue, Jul 15, 2014 at 7:04 AM, 'Terry Brown' via leo-editor
It seems that the uA persisting code really should try and save uA
info on nodes it can't match...
So what I was thinking was that the orphan nodes
As of rev 25101ddf3b0c... Leo now saves and restores clone links and uA's
in @auto trees!
For example, use the todo plugin to add an icon to a node in an @auto
file. Save the file and reload. The icon will still be there.
Ditto for clones links for between node a node C inside an @auto file
On Mon, Jul 14, 2014 at 8:48 AM, Edward K. Ream edream...@gmail.com wrote:
As of rev 25101ddf3b0c... Leo now saves and restores clone links and uA's in
@auto trees!
For example, use the todo plugin to add an icon to a node in an @auto file.
Save the file and reload. The icon will still be
On Mon, Jul 14, 2014 at 9:22 AM, Kent Tenney kten...@gmail.com wrote:
Such links should persist *provided* you don't change the outline structure
(including headlines) of the @auto file outside of Leo.
This is a show-stopper for me, and probably evidence of my outlier status.
I'm as likely
On Mon, Jul 14, 2014 at 9:52 AM, Edward K. Ream edream...@gmail.com wrote:
On Mon, Jul 14, 2014 at 9:22 AM, Kent Tenney kten...@gmail.com wrote:
Such links should persist *provided* you don't change the outline structure
(including headlines) of the @auto file outside of Leo.
This is a
On Mon, Jul 14, 2014 at 10:06 AM, Kent Tenney kten...@gmail.com wrote:
I think I see the problem.
Such links should persist *provided* you don't change the outline structure
(including headlines) of the @auto file outside of Leo.
I read this as changing outside Leo breaking the import, not
On Mon, 14 Jul 2014 06:48:18 -0700 (PDT)
Edward K. Ream edream...@gmail.com wrote:
As of rev 25101ddf3b0c... Leo now saves and restores clone links and
uA's in @auto trees!
For example, use the todo plugin to add an icon to a node in an @auto
file. Save the file and reload. The icon will
On Mon, Jul 14, 2014 at 10:11 AM, Edward K. Ream edream...@gmail.com wrote:
On Mon, Jul 14, 2014 at 10:06 AM, Kent Tenney kten...@gmail.com wrote:
I think I see the problem.
Such links should persist *provided* you don't change the outline
structure
(including headlines) of the @auto file
On Mon, Jul 14, 2014 at 10:41 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
So how hard does the new code try to recover from breakage?
At present, Leo attempts no error recovery.
Does it use the new indexed UNLs to fall-back on position index when
headlines fail?
I
On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney kten...@gmail.com wrote:
Whew! I'm glad we're on the same page now :-)
Indeed, hate to see fisticuffs on this list [-;
Yeah, I was about to give you a phone call ;-)
Initial test is REALLY exciting, in addition to complete support for the
On Mon, Jul 14, 2014 at 11:29 AM, Edward K. Ream edream...@gmail.com wrote:
On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney kten...@gmail.com wrote:
Whew! I'm glad we're on the same page now :-)
Indeed, hate to see fisticuffs on this list [-;
Yeah, I was about to give you a phone call ;-)
On Mon, 14 Jul 2014 11:29:19 -0500
Edward K. Ream edream...@gmail.com wrote:
On Mon, Jul 14, 2014 at 10:46 AM, Kent Tenney kten...@gmail.com
wrote:
Whew! I'm glad we're on the same page now :-)
Indeed, hate to see fisticuffs on this list [-;
Yeah, I was about to give you a phone
On Mon, Jul 14, 2014 at 11:49 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
I asked a vague question about the status of vc.find_absolute_unl_node
and vc.find_position_for_relative_unl the other day, what I meant was,
what do they do that g.recursiveUNLFind doesn't?
26 matches
Mail list logo
