Please describe exactly what you are doing. See if you can come up with a very condensed example (a small file with only a few nodes, for example). What do you want to achieve, what did you expect, and what actually happened?
Bear in mind the the entire Leo code base is contained in a few Leo outlines, many people every day open those outlines that contain thousands of @file files, and don't have these kind of troubles. Of course, that's not importing. But - ask Edward - entire trees of code get imported into Leo all the time, too. So it's probably just that you have something amiss in your picture of how things work. Let's help you get that straightened out. Gotta start simple! On Thursday, August 20, 2020 at 2:20:30 PM UTC-4, k-hen wrote: > > Is it possible to configure a non-sentinel file to be write-only? > > The file sync is making me very nervous because (and I'm sure I did > something wrong) the file didn't import correctly and blew away my changes. > Fortunately I had a backup but this just isn't acceptable for me :-/ > > What I think is happening is that the file can't write or writes > partially, then I have to kill Leo for one reason or another, then it's > importing that incorrect file and wiping out my changes. > > If I can't figure out a way around this, it's a deal breaker for me > unfortunately :-( > > > > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c1ea7b63-1380-4f92-b5fd-96c1a65928bco%40googlegroups.com.
