I guess I should explain my use-case for this persistantly saved session data...
My computers crash. My power goes out, my laptop runs of battery, X11 takes a nosedive. I don't want to lose anything by: forgetting to save forgetting to save before leaving the program even if autosave is autosaving but not defaultly when you arent focused on the program forgetting to save before killall -9 python because other stupid python processes like to have issues from time to time It is _Liberating_ to be able to just "stop typing" and know that 'whatever happens next, I won't lose this data, unless my SSD refuses to sync() the sync() write it was just given and the filesystem metadata goes sideways when XFS is abruptly power-cycled'. Mike On Fri, Jul 1, 2016 at 3:56 AM, Mike Hodson <[email protected]> wrote: > Hi again, > > Great program so-far, excellent featureset no other program can compare to, > but the small inconsistencies with regard to things that other programs do, > and this doesn't quite do, are nagging me. > > Like the non-default session storing feature. Which doesn't quite fit the > bill of saving "the entire session" but moreso "the visual orientation of > the windows that you last had open" > > To me, these are quite different things. > > I wrote up a bug because I expect anything with a session-saving feature, to > _automatically save the session_ the first time I try to close the program > without saving a file explicitly, and then relaunch with the prior session > reloaded. This is something I just expect by default, because the vast > majority of programs with a session feature operate in this manner. > > Further, the session saving ability for the program does not do similar > things with regard to Sub3/N++ : temporarily storing any unsaved content. > > I always am prompted to save my changes; i don't want to save the changes > unless I want to write the files; but i _do_ want some temporary > edit-buffer-state session saving. > > Test case: > > sublime3; > launch with subl3. > start typing anything random. > close it with mouse using window manager X button. > reopen it with subl3 > > This will cause your random typing to show up again, the same way you had it > before closing. It does not prompt for saving anything. It just knows "this > is how you left it" and restores everything. > > Notepad++ is also very similar but as I'm not natively on Windows, i won't > give you a similar list of steps to complete the same. > > Leo: > launch with launchLeo.py --sesson-save > create a new outline - untitled > type text > attempt to close window with window manager X button. > > dialog box for saving untitled comes up, -after- > wrote /home/mike/.leo/leo.session > occurs. > > So if I just kill python at this point, to get rid of the save window, the > session file is already written and causes a traceback upon starting the app > again with --session-restore. > > The session file contains: > ["/home/mike/.leo/workbook.leo#Leo's cheat sheet:1", "#NewHeadline:0"]m > > Which to me, seems to imply this is honestly not a "session" but a "tab > layout" saving plugin. > > Unfortunate :( > > > -- > 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 post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
