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 working on *last* that’s important, not whatever ones I hardcode into a script.  I use Leo for dozens of reasons, which fluctuate all the time.  I’m going to seriously lose a lot of joy if I have to constantly hunt down which files I was working on last.  Yes, the recent files list helps, but it’s still a lot of unnecessary end-user friction to have to manually open them all up on each start up.

Just my $0.02.

Jake

On Jun 29, 2023, at 8:22 PM, Mike Hodson <myst...@gmail.com> wrote:


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 document, there should be a state file saved on the disk, that keeps the state of the open draft and relates it to an open session.

If my power fails two seconds later I expect to be able to load Leo up and get the exact point where I left off.

I haven't used Leo seriously for the last 5 years because of this lack of functionality.

Mike


On Thu, Jun 29, 2023, 16:06 Edward K. Ream <edream...@gmail.com> wrote:

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 method, but I shall retire the entire class instead.


The SessionManager supports six session-* commands. The commands allow you to specify a set of files to open at startup. But listing the desired files (in a shell script or .cmd file) is simple and good.


Summary


The session-* commands are absurd solutions to a non-existent problem. This class significantly complicates Leo's startup logic. The entire SessionManager class must go. Félix take note :-)


As a side effect, Leo will no longer write ~/.leo/leo.session


Your comments are welcome. Good luck arguing for this class :-)


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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/5480a75d-ada7-4bb0-8a4b-b27c8fe5486an%40googlegroups.com.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAN%2B%2B4hFrZhEmhKD14q7hXufSTjJ95Q9QH-uESxcJgD0TmnPUeg%40mail.gmail.com.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/65A3D6D3-A330-4FB5-AB07-13B7F08089EF%40gmail.com.

Reply via email to