Sorry for the extended intro, skip to the bottom for a concise question if the topic isn't of interest.
For a variety of reasons, all my own fault I'm sure, I've got two relatively large Leo files that have gotten out of sync with the external files in my filesystem, including hundreds of the scary "...has been modified outside of Leo. Overwrite this file?" and unfortunately I haven't updated since this was fixed<https://groups.google.com/d/msg/leo-editor/2vWBrODehx4/tI7v0QM6ybcJ>, and with all the "interesting" developments will probably hold off for the moment. Unfortunately I didn't properly follow my own SOP, with help from Terry's script <https://groups.google.com/d/msg/leo-editor/-COzMKFwNmg/9Rr2T3H-G8gJ>, to ensure that all my content nodes in the .leo data is replicated out into the external files, so I can't just delete the .leo files and start over. So I've decided to empty them out manually, carefully comparing with the externals, checking for clones (now straight duplicated content in the externals) and most importantly data that only exists in the .leo, creating external files manually to store it. I plan to rely on the external filesystem only for the moment, but will be experimenting with Zim <http://zim-wiki.org/>, which is probably more "my speed" for this particular use case, easily handles cross-file linking to reduce the need for cloning, apparently supports content-tagging in a relatively user-friendly way, and happily is also written in Python. The only (minor) issue is that it has its own "proprietary" markup syntax, but the author is working on an export routine to pandoc<http://johnmacfarlane.net/pandoc/>'s extended markdown, which should at least in future handle exporting to EPUB, websites, DocBook etc. (he could just as easily used reST to get into pandoc, but chose markdown instead). My question - once I've emptied and deleted these two current .leo files and am managing the content externally, is there a recommended way to use Leo (presumably with activepath) so that I can automate bringing the whole dirstruc tree in so that it's all "read-only" AFA Leo is concerned? I then want to be able to refactor externally - rename folders and files, add/delete move directory branches around in the filesystem, maybe not open Leo for weeks, and then when I do, everything is updated and brought in sync. If I have to manually maintain stuff in Leo to match my often-changing tree with hundreds of files, I'll probably wait until things settle down and see how Zim goes first. . . TIA -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/72RzNzwztnkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
