On Tue, Dec 10, 2013 at 11:24 AM, Fidel N <[email protected]> wrote:

>
> Its never intuitive to know who is the "boss", meaning, if I edit a file
> outside Leo, but a leo outline is open with the file, who wins? How will my
> data change? What will I have to do to go back to original? Undo??
>

This is hardly Leo's problem.  It is the well-known "multiple-update"
problem.  All bets are off unless you use the xemacs or vim plugin to
coordinate Leo with the other editor.

In general, when two programs have copies of the same data, the last
program to write the data wins.  There is no way around this with present
file systems.

The only way for me to go down that road will be when I can click a Leo
> button that will give me for instance, 3 options, telling me the summary of
> differences, for instance:
>

My experience shows that this is a truly bad idea.  Typically, when
confronted with this choice in the past I have experienced panic.  Even
when I was the one who created the button (or dialog)! The problem is that
the dialog is unexpected, and I never feel like I have enough data to make
the proper choices.

In short, trying to sort out data conflicts is *hopeless*.  The only
solution is not to get into those situations.  If your work flow requires
having lots of files open in other editors, don't even *think* of making
those files into @auto or @file nodes.  Leo is not the appropriate tool in
those cases!

Edward

P.S.  This may surprise some, but let me say for the
I-don't-know-how-manyth-time that it's perfectly all right with me if there
are some situations in which people *don't* use Leo ;-)

EKR

-- 
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/groups/opt_out.

Reply via email to