> > If the reason for not using @file-node-clones is because of the risk of > data loss, then my next question becomes "why is there a risk of data > loss?" If the answer to this is due to some fundamental property of > outlines containing clones, then I'd like to understand that better so that > I can work accordingly. If that is not the case however, then the > underlying cause of data loss should be addressed, rather than to simply > adhere to a convention of not using @file-node-clones. >
I am not 100% sure, but I believe that this restriction is dictated with the present read or write algorithm. IIRC few months ago when I was experimenting with the new read/write algorithm I have realized that with the new algorithm that restriction can be removed. However, this new read/write algorithm is not incorporated into Leo yet. The experimental code can be found here <https://github.com/leo-editor/snippets/raw/master/experiments/line-numbering.leo> . One solution could be to use symbolic links instead of real files in other directories (that is what I usually use). Or you can write a plugin (or script) that registers 'save2' handler which is invoked after outline is saved and in the handler make copies of external files. Vitalije -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
