What should happen to currently opened files if you choose to load a session - are they closed, or do they remain open? What about new files that have been created but not yet saved?
jps wrote:I can see a few options for how it could work, none of which would result is the user losing any work:
#1: Changing sessions is like changing profiles: sessions contain the complete state of the editor (open files and their modifications, as well as open windows and their positions), and changing session will close all open files and switch entirely to the new one. This would work behind the scenes just like 'File/Exit and preserve session': state, such as unsaved changes to open files, would be saved in the session.
#2: Sessions apply to a window at a time only. Opening a new session will open a new window with that session. It allows multiple sessions to be open at the same time, but perhaps doesn't make sense if you want one session to span multiple windows.
#3: Making sessions a bit 'softer': Opening a session closes all opened but un-modified files, while leaving modified files alone. Files that were open in the session are then opened. Window state, layout, find history etc aren't touched.
I think #3 is my favourite, but I'm not sure that any of the above are really satisfying.
sublimator wrote:EJ12N: Check out Steve's AutomaticBackups plugin if you haven't already. Really handy.
EJ12N wrote:This little feature has saved me a couple times already, I love the fact it saves unsaved files!
sublimator wrote:EJ12N: Yeah, they are complementary. The auto backup saves a time stamped version of each save, kind of like an automatic commit for a rudimentary version control. Works quite well. Has ctrl+alt+[ or ] to rewind/fast forward through history.
jps wrote:If I'm allowed to have favourite features, this would be one of them - I've got unsaved files with notes etc that I started editing months ago, and have yet to get around to explicitly saving them.
Users browsing this forum: Yahoo [Bot] and 4 guests