Re: Merged sqlite-leo branch in master
Hello Sir, I think your work is brilliant, although I am not able to understand many things, and I have not gone over it in detail. Still, I am sure from what I do know that it's groundbreaking and fascinating! I suggest a possible collaboration (if I have anything to offer). I am just an amateur but I have created 'leo4sqlite' and you might find something interesting there. Hopefully you will have a little advice for me either way! You can find it here: https://www.github.com/tscv11/leo4sqlite Please feel free to post or send a message if you ever have a question, and if there's anything you need (sqlite3-related) please let me know! Thanks for your time! tscv11 -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Merged sqlite-leo branch in master
This is very strange. When I put your leoPy.leo in my leo/core/ folder, I can open it without any problem. Writing all files under Code reports all unchanged files, and: git status gives no changed files at all. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Merged sqlite-leo branch in master
On Sat, Aug 12, 2017 at 7:48 AM, Edward K. Reamwrote: > > > On Sat, Aug 12, 2017 at 7:25 AM, vitalije wrote: > > The only thing that comes in my mind is that when g.SQLITE is true, >> retrieving from cache is skipped. Can you test once again clearing cache, >> then git checkout -f, so that all external files are unchanged and then >> open LeoPy.leo? >> > > Yes, -f works. I don't understand why. > I spoke too soon. When I reload leoPy.leo, using the cache, the code disappears again. Edward -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Merged sqlite-leo branch in master
On Sat, Aug 12, 2017 at 7:25 AM, vitalijewrote: The only thing that comes in my mind is that when g.SQLITE is true, > retrieving from cache is skipped. Can you test once again clearing cache, > then git checkout -f, so that all external files are unchanged and then > open LeoPy.leo? > Yes, -f works. I don't understand why. Edward -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Merged sqlite-leo branch in master
On Saturday, August 12, 2017 at 1:52:00 PM UTC+2, Edward K. Ream wrote: > > On Sat, Aug 12, 2017 at 6:19 AM, vitalije> wrote: > > Something is not right. When load my local copy of leoPy.leo, @file > leoAtFile.py does not contain checkExternalFileAgainstDb. > > I see this method (in an external editor), in the node: > #@+node:vitalije.20170701155512.1: *6* at.checkExternalFileAgainstDb > > Clearing all caches does not help. Such a thing has never happened before. > > Saving the .leo file deletes the node from the external file. git > checkout leo restores it. > > Vitalije, what might be causing this? > > Edward > > Have you tried opening LeoPyRef.leo? Is it possible that some plugin that you have enabled and I don't can cause this difference? I hope we can find what is causing this strange thing, but it is something that I was complaining in #538 and #540. Perhaps it is not usual thing that you encounter this problem, because most of the time your copy of LeoPy.leo is fresher and richer than copy of others. The only thing that comes in my mind is that when g.SQLITE is true, retrieving from cache is skipped. Can you test once again clearing cache, then git checkout -f, so that all external files are unchanged and then open LeoPy.leo? -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
Re: Merged sqlite-leo branch in master
On Sat, Aug 12, 2017 at 6:19 AM, vitalijewrote: Something is not right. When load my local copy of leoPy.leo, @file leoAtFile.py does not contain checkExternalFileAgainstDb. I see this method (in an external editor), in the node: #@+node:vitalije.20170701155512.1: *6* at.checkExternalFileAgainstDb Clearing all caches does not help. Such a thing has never happened before. Saving the .leo file deletes the node from the external file. git checkout leo restores it. Vitalije, what might be causing this? Edward -- 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 post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.