What is the status of addressing 'refresh from disk' on @auto nodes?
I recently did some editing outside Leo on an @auto file, refresh failed,
I removed the @ignore line and refreshed again. This appends a copy
of the file contents to the end of the file, leading to much confusion.
Skimming this
On Sun, Dec 8, 2013 at 8:24 AM, Kent Tenney kten...@gmail.com wrote:
Skimming this thread, it appears that if I want to edit an @auto file
outside Leo, I should close Leo, edit the file, re-open Leo.
Is this the resolution?
I wouldn't call it a resolution; I'd call it the basis of a bug
I use refresh-from-disk to sync outline with files I edited elsewhere.
Maybe we could use different string (load from disk) for new nodes?
On Sep 26, 2013 7:51 PM, Edward K. Ream edream...@gmail.com wrote:
Refresh from disk is the feature of Ville's contextmenu plugin that I use
the most. This
Hmmm, looks like this explains how I lost information in a file I worked on
for several hours yesterday. I didn't know that refresh-from-disk was
dangerous. I use it in a shared file setting with another person.
Considering your workflow use to populate an empty @file node, why is that
Hello,
has anyone considered storing SHA hashes of node's text inside the
sentinels so that Leo can much more intelligently decide what to do in case
of such conflicts? It would also help with clone wars. I don't use clones
at all currently despite they are very desirable feature. Since I
On Tue, Oct 15, 2013 at 9:35 AM, Juraj rin...@gmail.com wrote:
has anyone considered storing SHA hashes of node's text inside the
sentinels so that Leo can much more intelligently decide what to do in case
of such conflicts? It would also help with clone wars.
This has no chance of working.
On Thu, Sep 26, 2013 at 9:51 AM, Edward K. Ream edream...@gmail.com wrote:
BTW, there is always a workaround to problems with refresh-from-disk.
Simply save the .leo file and reload. The save will be safe for never-read
@file nodes, provided that you say no when asked whether you want to
Refresh from disk is the feature of Ville's contextmenu plugin that I use
the most. This post proposes a way to use refresh-from-disk safely, or
mostly so.
Any change discussed here will happen after b1 goes out the door, so there
is plenty of time for discussion. I encourage your comments.