In any case, now I know that Leo doesn't officially support the .db3 file format. I will try to discover how I made it happen anyway.
If you think of *anything* (at all) that could've caused Leo to produce the attached document please let me know! Thank-you for your help and your work on Leo - I understand that you can only do what you can do, as they (inanely) say On Tuesday, May 2, 2017 at 3:09:11 PM UTC-7, tscv11 wrote: > > The "import->import any file" method for .db3 files no longer > works for me, and does, in fact create completely empty nodes titled > after the file (@auto nodes). Thus I cannot repeat the process, and I > was hoping someone could figure out how I got that result, if Leo > *doesn't* > support .db3 files. And trust me, I have better things to do than make > up stories for Leo developers. I can't repeat it, but it *did happen* ; ) > > With sqlite3 files importable as xml (as shown) I knew it would be > relatively > easy to write my plugin, so hopefully you can understand my disappointment > upon finding that the imports no longer worked, and why I asked for help. > > > Hmm, SQLite files are binary and I don't remember Leo having any > >> support for them, so wouldn't have expected that to do anything useful >> - can you verify you can do it repeatably? >> >> Building an outline in Leo based on the content of SQLite file with a >> Python script wouldn't be too hard, but you'd need to know the >> structure of the data in the SQLite file and how you wanted to map it >> to Leo's tree. >> >> Cheers -Terry >> > -- 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.
