I've had a few errors already but they have only been partly repeatable. The context is that I have an outline that contains an *@clean README.txt* node. Currently its text displays with blue color which is not what I want. So I opened the node in an external editor with Leo also open and the outline selected.
I added a new line to the top of the file in the external editor: *@nocolor*. Leo picked up the change, added the changed notification and clones, and displayed the text in white. So far so good. Then I did the inverse - removed the *@nocolor* line using the external editor. Here's where I started to have problems. I've tried cycling through this change several times. Once Leo crashed when I tried to navigate between the clone and the original node position using the forward-back arrows. Once the change didn't appear in the original node. There are a lot of mix-and-match combinations, and I haven't tried them all systematically yet: Save the outline between operations, or not; delete the clone nodes or not; edit the *@nocolor *line in or out in Leo and then do the opposite in the external editor; ... I can't be more definite yet because I haven't been systematic enough but I have definitely had erroneous operations. On Tuesday, July 15, 2025 at 7:58:58 AM UTC-4 Edward K. Ream wrote: > On Tuesday, July 15, 2025 at 6:55:02 AM UTC-5 Edward K. Ream wrote: > > > > Deleting any part of [the update report tree] has affect any external > file. > > > Oops: I should have said: > > > Deleting any part of this tree has *no affect** on* any external file. > > > Edward > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/9b56310a-355b-4c71-9638-b04e6fe9d6cbn%40googlegroups.com.
