> 3 versions exist, Leo buffer, vim buffer and disk version... Yep. So you are correct that simultaneous changes to both the vim buffer and leo buffer will conflict but whichever app next saves its buffer, the other app will notify the user and ask whether to refresh or not. That works for me even though you could lose a change depending on your workflow. Note the advantage to me is that the vim version of the file may be one of a N open buffers in vim and may appear N times in various vim windows.
I do think that the other capability you want is to be able to open a single node body in an external editor and then you would use a temp file and update in real-time. Ideally Leo would have both these capabilities to interact with external editors and they would be independent of the choice of external editor (other than you'll have to point Leo to the editor you want to use). -- 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.
