On Wed, 12 Feb 2020 13:21:10 -0800 (PST) Thomas Passin <tbp100...@gmail.com> wrote:
> On Tuesday, February 11, 2020 at 11:55:38 AM UTC-5, stevelitt wrote: > > > > On Sat, 18 Jan 2020 15:36:36 -0800 (PST) > > andyjim <andy...@gmail.com <javascript:>> wrote: > > > > > > > My thought is to arrange all this in external plain text files > > > initially, with the outline organization being in Leo, leaving > > > the files external > > > > Hi andyjim, > > > > The thread you started long ago moved away from the preceding > > desire. Your preceding desire should be very easy to accomplish > > using the same method VimOutliner accomplished it: Use executable > > lines. Somewhere on a headline, or as a direct child of a headline, > > have a command to view the external file, so that if you hotkey the > > headline, it runs the command and pulls up the file. > > > > @stevelitt, I agree that there are many ways a system might be > implemented. One of the things we (or I, anyway) are keeping in mind > is a strong desire to be able to extract the data from the system in > case it has to be used in some other system (or even manually, in the > worst case). >From the preceding, I assume all the information is not within the same directory tree, so you can't just roll it into a tarball. And if it isn't already in Leo, it sounds like you don't yet have an inventory of all this information. If this is indeed the situation, you have a challenge: A very interesting one. Please feel free to contact me offlist for the parts of the situation not involving Leo: If the situation is what I think it is, it's very interesting and common situation whose solution isn't trivial. > So at this point, we're trying to get clear on the > concept of operations (use the use cases, if you like that > terminology better), and then see how we can fit that into Leo. Bear > in mind that we're thinking about a substantial body of work here - > potentially years or decades of research and thinking. The primary > objectives are to be able to preserve that work, Sounds to me like you need to identify each file to preserve the work. Perhaps you can then put a hard link, of the same name but different directory, to each file within a directory tree meant only for this body of work. Then you can back it up with tar. > to be able to add to > it with the least amount of friction, and to use have the system help > us use it in a way that promotes creativity and productivity. Sounds like Leo to me. Probably write a small, possibly recursive program, to turn them all into a .leo file, and then put the headlines from that .leo file in the appropriate parts of your master Leo file. > > An additional constraint is that both @andyjim and myself want to be > able to get these notes and their meta data into the system with the > least hindrance possible - a stream of plain typing being the most > desirable. I'd use a little program, and if doesn't give you the exact desired format, edit it with Vim until it does. > > After that, I expect we'll be getting into user interfaces, and what > compromises might be forced on us - let's hope they will be minimal! > That's where your ideas could fit in. > Sounds good! SteveT Steve Litt February 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive -- 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 on the web visit https://groups.google.com/d/msgid/leo-editor/20200212213201.2f246b50%40mydesk.domain.cxm.
