My sincerest apologies if I came off too alarmist with this message, this is an awesome community and Leo is a truly amazing tool and ecosystem. Rest assured I'm certain the problems are with *me* and not the software :-)
I still believe there would be a huge amount of value in a file type that is write-only and not synchronized with the filesystem. In fact I want to pick up changes with many small @auto nodes and then clone the content of those nodes and embed them into *multiple* separate @write nodes and thus avoid the 'clone wars' (among other things). I think the @rst directive maybe does this and perhaps the @adoc one can do that too, but it wouldn't really solve the whole issue since some of the output files would include additional file formats. I'll try to put together a simple walk through and use case. Thanks again for your patience. Kevin On Thu, 2020-08-20 at 13:13 -0700, Félix wrote: > If I may suggest : A quick [Alt+PrintScreen], on any OS, will capture > the currently focused program window as a picture. > > Under windows, its in your clipboard so you can just CTRL+V to paste > right in here while you type. Like this: > > (In linux its put into your home/picture folder. ) > > So I would recommend you paste one before, and at each step of the > behavior/actions your trying to illustrate with your textual > description. This will allow experienced users to spot instantly some > details that explains the behavior you're experiencing while using > Leo. > -- > Félix > > > > On Thursday, August 20, 2020 at 3:31:18 PM UTC-4, Thomas Passin > wrote: > > 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 a topic in > the Google Groups "leo-editor" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/leo-editor/yo1p0tkOCDg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/leo-editor/292fb4c0-aea6-48d8-9062-df042d4d2c00o%40googlegroups.com > . -- 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/ec686cf12ff8ae7b93034daede2c71ebecde8143.camel%40gmail.com.
