On Mon, Jul 14, 2014 at 9:52 AM, Edward K. Ream <[email protected]> wrote: > On Mon, Jul 14, 2014 at 9:22 AM, Kent Tenney <[email protected]> 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 to work in vim as Leo, on-the-run work done in vim, more formal >> sessions from Leo. If changes outside Leo break @auto, it's no longer @auto >> in my book. > > I think you will find that the present scheme will work well for you. > Please try it. > >> The question seems to be: 'which is canonical, myfile.py, or myfile.leo' for >> true leonistas, the latter is fine, I need the former. > > myfile.py *is* canonical, if I understand you correctly. The new > @auto is exactly the same as the old @auto in this regard. The parser > hasn't changed: you *always* get the outline structure of the imported > file. Period. > > Persisted data have got to be stored somewhere. In the present > scheme, they are stored in the @persistence tree, but it really > doesn't matter where the data are stored. Putting them in a db > changes nothing. > > The question isn't which data is canonical, the question is how to > link data with incoming nodes. > >> All this means is that you are solving a problem that I don't have, but one >> that presumably, many others do. > > I have solved the one and only problem that we have been talking about > for these many years: how to associate uA's and clone links with > imported outlines. > > You are asking for the impossible if you demand that the links between > persisted data and incoming nodes *never* break. Only sentinels with > gnx's provide truly unbreakable links.
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 just the inevitable issue of 'here's an unknown node'. I bet the changed nodes get a fresh gnx and a blank uA correct? As you say, that's all that is possible. Sorry for the noise. > > Bookmarks (unl's) along with a flexible (but not perfect) algorithm > that associates the unl's of incoming nodes with gnx's (and hence, > persisted data) seem like the only possible approach. If you want > something better than bookmarks, please explain how it might possibly > work. > > Edward > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
