Very cool - sounds like something I'll be using soon then - thanks! On Friday, August 21, 2020 at 3:16:06 PM UTC-4 vitalije wrote:
> leo-ver-serv will store all the history of Leo files in the sqlite3 > database files named after the original Leo files, just with added > '.history'. If for example you edit workbook.leo file, leo-ver-serv will > store changes to workbook.leo.history in the same folder. > > Vitalije > > On Friday, August 21, 2020 at 8:53:29 PM UTC+2, k-hen wrote: >> >> Excellent, I'll check it out - thanks! - do you happen to know if that >> history_tracer works with the sqlite/db back-end? >> Re: interrupt, that's great news too - in addition to just Leo functions, >> if/when I get database queries working, being able to cancel the command is >> a relatively critical use case there too :-) >> >> Kevin >> >> >> On Friday, August 21, 2020 at 1:24:43 PM UTC-4 vitalije wrote: >> >>> >>> >>> On Friday, August 21, 2020 at 4:14:43 PM UTC+2, k-hen wrote: >>>> >>>> Yes, absolutely, I'm a huge proponent of Git and it's toolchain :-) >>>> That said I want my personal comments and notes and settings *outside* >>>> of git and not checked in as well. >>>> So I need both regular backups/protection for Leo in _addition_ to the >>>> Git repo which is synced with other devs. >>>> >>>> >>> I am not sure this is relevant, but there is a history_tracer plug-in >>> which takes snapshots of your Leo files after each change. That is >>> something like making git commit after each edit. You need to have >>> leo-ver-serv program running and your Leo documents must be on the list of >>> files that leo-ver-serv should keep an eye on. >>> >>> By the way, I would also like that we could interrupt Leo without >>> killing it. On several occasions I missed that functionality. I've added >>> support for interrupting the execute-script command in Leo, and it wouldn't >>> be so hard to support many other commands. I don't have the time to do it >>> myself right now, but I guess it would be sufficient to add try/except >>> KeyboardInterrupt pair around some global method that executes commands. >>> This might not cover all commands, but it certainly would cover a lot of >>> them. Edward was recently refactoring key handling code and I believe there >>> is a method something like a main command handler there. >>> >>> Vitalije >>> >> -- 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/3da4ceb1-ce7b-46e3-b48b-18bb1d272d73n%40googlegroups.com.
