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.
test.leo
Description: Binary data
