No no no, how can you say that when I have tested (and am testing right now again, since one hour), to save projects/workspace and reopen things in dozen ways ? Do you know any softwares that requires to test things dozens of time ?
That's not the fault of users if Sublime-Text is completly bugging and not intuitive at all, many users have talked about it on this forum, and you don't have to patronize me and give your opinion like that without giving any damn proceeding.
So, as you are lazy and I'm not, I'm going to re-explain what I've re-tested today, wich definitley proves that ST3 has no real session-saving but a messy parameters synergy.
My texts are not so long, and they are very well bullet-listed and numbered, so anybody can ead it clearly :
CONCEPTION OF THE TEST
I decided to slice things in 3 parts for my project : one window with X folders added on the left and some tabs, one other window with different folders, and a third one with again different folders and tabs. So doing, things will be more clear (and saying that I confuse things is a provocation, giving that any other software save entire set of windows correclty, or separated ones, without any kind of bug. Rejecting thing on users is a real joke).
FIRST TEST : SAVING TEST
To proceed to this test, I've created each window separately, one after the other. Proceeding was, exactly :
- Open ST3,
- Close anything preceding the test that was re-opened automatically ("Project -> Close Project" if needed),
- Add folders to the actual blank project,
- Open some tabs,
- Save the project in a sublime-project file. Right after having saved the sublime-project file for the first window, I tried to save the workspace too, but noticed that it has already be done ! "Fine", I said !
- Close the window by pressing the red cross (I don't want to lose time by any other superfluous menus ; if ST3 has a problem with that, it's not user's fault. Things work well in zillions of softwares around the globe).
SECOND TEST : REOPENING TEST
I click on on of the three sublime-project files, and noticed that it reopened the workspace of the "project" too. (please do not quote and comment that as a ridiculous obviousness : at this point, nothing is obvious with ST3. I don't know how you do, but we're not in your head !). I closed the unique window I had opened.
So I decided to focus on sublime-project files, and created 3 shortcuts to made my reopening test.
I first reopened the same project : it worked. Then I closed it again, and opened a second one : oh damn ! It reopened the last project at the same time... Ok, so I started to doubt of the positive evolution of things since my last post a few months ago.
I retried in different ways to close and open things, and each time the last closed window was remembered, and reopened with the different project launched by the shortcut.
I remembered that there was two options acting on the saving/reopening process, so I started a new pattern of testing.
REOPENING TEST WITH VARIATIONS OF "HOT_EXIT" AND "REMEMBER_OPEN_FILES"
The first variable is offocial, but the second one is unfindable in the ST3 main setting file. So I simply added both to my user setting file.
COMBINATIONS AND OBSERVATIONS #1 :
"hot_exit" : true,
1. Window (of the project opened during this setting up), is saved and restored (if I relaunch the same project).
2. "Last window" memory-effect : the same aforementioned project is reopened if I launch an other one ! (wich is annoying, because it forces us to close it. Who wants to open the last project when opening a specific different one ?).
Note : remember_open_files seems to have no effect (intuition : maybe hot_exit makes workspace to be saved in addition to saving "unsaved" data of tabs ; wich is different, I have to recall it !).
COMBINATIONS AND OBSERVATIONS #2 :
"hot_exit" : false,
1. Window of the previous project (used during setting up variables) is not saved and not restored.
2. No last-window-memory effect ! If I launch an other project (still not affected by this loss of memory), the last opened project is not reopened !
3. Any blank window neither.
Backfire : projects windows are not saved anymore ! Wich means that if I close the window at this point of the test (without changing the variables for preparing the next test), I will lose a second project ! And so on, until all the three will be wiped !
So I quickly change variables before closing the window...
COMBINATIONS AND OBSERVATIONS #3 :
"hot_exit" : false,
1. Window correctly saved and restored.
2. Last-window-memory effect
At this time, it seems that we're in the same situation that in #1.
COMBINATIONS AND OBSERVATIONS #4 :
"hot_exit" : true,
Same as #1 and #3 !
So, only setting up the two variables produces the "wipe" effect (I call this like that, because sincerely, the combination of trying to reopen last things WHILE not saving the actual ones is kind of a nuke reaction made for ruining our mental heatlh ).
Now, I have to try two more things to be sure.
COMBINATIONS AND OBSERVATIONS #5 :
I delete the "rememberopen_files_" of my user setting file, giving that it is not official, and stick with the only save-related feature wich is "hot_exit" :
"hot_exit" : TRUE,
Same as #1 and #3.
So, hot_exit is not only a question of exiting quickly and saving tabs : it seems to be confusely used as a saving session (workspace, wich means windows and tabs). And don't say me I haven't understood the feature ! No other variable is found in the setting system to simply activate/deactivate the "reopen last-closed window".
I recall that there is three different things :
- saving a set of windows and tabs (no variable found at this moment)
- saving unsaved data in closed tabs (wich I assume is the first function ot hot-exit, wich would rest on a saving feature to have sense)
- reopening the last closed window.
At this moment, ST3 is completly confusing these 3 things in one single variable...
Anyway... user's are always guilty, hmm ? (sic)
COMBINATIONS AND OBSERVATIONS #6 :
"hot_exit" : FALSE,
Wipe all, remember nothing. Like in #2.
Now, it's clear that my assertion that ST3 mixes three different features in the hot-exit variable is true.
It seems that if we close a project, and reopen the same project, ST3 try to use the "reopen last window" function and opens a new blank window in addition (and focused in foreground) to the... already opened project ! It's kind of redundant...
It definitly shows how the "memory-effect" is annoying and messing things up (particularely when last project window is reopened in situation of "not saving the last closed window", wich results in wiping it ).
Clap clap clap... Not only users don't know if they have to click on sublime-project files or sublime-workspace ones, but the entire system resting on the single "hot_exit" variable is unreliable !
I wait for responsible answers from the ST3 staff, and not from kids around who can't accept that someone doesn't blindly defend the product, and who patronize people by repeating "you don't know how to use it".
Especially when no effort is done to explain how to use it. Ok ?