Re: Heads up: The SessionManager class will go away

I will second this desire. I really like being able to restart Leo and pick up right where I left off. I think that has been a very positive trait of Leo. In fact, it gives the user - or at least me - a sense that Leo is especially well engineered and that user needs have been carefully thou

Re: Heads up: The SessionManager class will go away

I would argue that Edward’s solution of ‘just list the files you want to open in a script’ to totally not capture the essence of the session.  The whole point of sessions to me is to keep the flow of what I was doing last.  It’s more than a set of static leo files.  It’s the set of leo files I was

Re: Heads up: The SessionManager class will go away

Out of curiosity why is the function of a session considered obsolete? This is what I have needed forever, a proper reloading session that automatically saves and does not lose data, regardless if I might have three drafts open that have yet to be saved to disk. The instant I create a new documen

Re: Heads Up - My Workbook Is Getting Destroyed

On Thu, Jun 29, 2023 at 4:41 PM Thomas Passin wrote: > Even though I dislike PRs that are very complicated and try to do too many > things, I have to agree in this case. > Thanks :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To un

Heads up: The SessionManager class will go away

Leo no longer supports --session-restore and --session-save. LM.scanOptions lists them as obsolete. But the *SessionManager* class still exists. *SM.load_session* is the culprit behind #3404 . It would be straightforward to fix this meth

Re: Heads Up - My Workbook Is Getting Destroyed

Even though I dislike PRs that are very complicated and try to do too many things, I have to agree in this case. On Thursday, June 29, 2023 at 5:37:32 PM UTC-4 Edward K. Ream wrote: > On Thursday, June 29, 2023 at 3:43:22 AM UTC-5 Edward K. Ream wrote: > > > See #3404

Re: Heads Up - My Workbook Is Getting Destroyed

On Thursday, June 29, 2023 at 3:43:22 AM UTC-5 Edward K. Ream wrote: > See #3404 . The first comment of the issue discusses the failure and how to fix it. > PR #3215 may as well clean up th

Edward K. Ream, Could you record some of your daily workflow?

Dear, Edward K. Ream, I believe your daily workflows is an invaluable asset, as well as leo-editor. Even the doc and Leo files contain lots of information there, but there are still lack of your workflow of Leo. For example, in doc Lesson 7: How to make complex changes to a code base

Re: Heads Up - My Workbook Is Getting Destroyed

On Thursday, June 29, 2023 at 2:10:26 AM UTC-5 Edward K. Ream wrote: See #3404 . The first comment of the issue discusses the failure and how to fix it. ... PR #3215 may as well clean

Re: Why does leo asks to restart when a .leo file modification is detected? (instead of asking to reload the file?)

On Wed, Jun 28, 2023 at 10:49 PM Félix wrote: > Exactly as per the subject line, I'm wondering why does Leo asks to > restart when a .leo file modification is detected? Instead of asking to > reload the file? I don't know. The only way to find out is to change the code and see what happens. Rea

Re: Why does leo asks to restart when a .leo file modification is detected? (instead of asking to reload the file?)

I've wondered about this, too. It seems obvious to me that if LeoPyRef has been changed outside of the Leo session that Leo should restart. This could happen, e.g., if the user checks out a different branch of leo-editor or updates the current branch. For other outlines, maybe the thinking wa

Re: Heads Up - My Workbook Is Getting Destroyed

On Tuesday, June 27, 2023 at 4:55:37 PM UTC-5 Thomas wrote: > I haven't filed an issue on this yet because I haven't got all the conditions nailed down. See #3404 . The first comment of the issue discusses the failure and how to fix it. T