On Sat, Feb 13, 2010 at 9:24 AM, Kent Tenney <[email protected]> wrote: > create new Leo file > > create node @auto /tmp/foo.txt > > enter text in body > "line 1" > > <ctrl-s> > > at prompt, save as /tmp/foo.leo > > rclick node, select "Edit /tmp/foo.txt in gvim" > > change contents to > line 1 > line 2 > > save file, exit gvim > > node body shows > line 1 > > rclick select "Refresh from disk" > > body shows > @nocolor > line 1 > line 2 > > <ctl-s> > > dialog "/tmp/foo.txt has been modified outside Leo, overwrite?" > > Seems buggy.
I wouldn't call it buggy. Clumsy might be a better word. I presume you mean that if you are using the "Refresh from disk" command that you already know that the file has been changed outside of Leo. Otoh, an alternate point of view would be that you could use the "Refresh from disk" to determine whether a file has, in fact, been altered. In that case, the prompt tells you something you didn't know. In any case, this is an rClick issue, not a core Leo issue. Anyone have any other thoughts about what rClick should do? I don't care either way. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
