Hi Phil,
I replicated the only-1-copy-written behaviour here with both @file and
@clean cloned nodes.
I used to use cloned @file nodes in order to always have same copy of
`thing.py` in my development folder and in a shared system path. It saved
me from having to keep running a deploy script to update the copy. I really
liked that! Until... something weird happened and both copies got messed
up. And then a few weeks later it happened again. Edward explained that he
really didn't like cloned @file/@thin/@shadow/... nodes because of
{...cache problems? race conditions?} and possibility of data loss. (whee!
I found it)
The advised pattern is to have distinct `@file path1/thing` and `@file
path2/thing` head nodes and then create an organizer node inside each and
clone that instead.
This was a couple years ago. I don't know what might have changed since
then.
-Matt
On Mon, Nov 6, 2017 at 12:49 PM, Phil <[email protected]> wrote:
> Leo 5.6, build 20171105131700, Sun Nov 5 13:17:00 PST 2017
> Git repo info: branch = master, commit = 94ebac1f2510
> Python 2.7.13, PyQt version 5.6.2
> Windows 7 AMD64 (build 6.1.7601) SP1
> isPython3: False
> caching enabled
>
> Place the attached file in a folder containing empty subdirectories sub1
> and sub2. Then open the .leo file and do the following:
>
> 1) Select the test.c node under the sub1 path, make an edit to the body,
> and save the file. The file test.c will be created in directory sub1, but
> not in sub2.
>
> 2) Select the test.c node under the sub2 path, make an edit to the body,
> and save the file. The file test.c in directory sub1 will be modified, but
> there will be no file created in directory sub2.
>
> 3) With the test.c node under the sub2 path still selected, make an edit
> to the body, then save using Ctrl-Shift-W. The file test.c will be created
> in directory sub2 with the new edits, but the file in directory sub1 will
> not be updated.
>
> This behavior does not match what used to happen in the past (maybe more
> than a year ago). It used to be the case that changing a cloned @file-like
> node would result in those changes being saved to all the paths under which
> the clone lived in the Leo outline.
>
> I just recently switched to using the GIT repo as my Leo install, so maybe
> I lost a setting in that switch. Or maybe Leo's behavior changed. Either
> way, I'd like it to be what it used to be. Any suggestions?
>
> Thanks!
> Phil
>
> --
> 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.
>
--
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.
