Quote
JamesD
... or if your post violates some other check. It is not directed at you, but is just trying to keep the forum safe and clean of spam.
Thanks; that got clear as I was aware that I just copied the entire title as first sentence. Isn't it possible to include a hint in the warning message that the first sentence of the main text are not allowed to be the same or (something like that)? Or offer a hint or link to the help file where is described when that situation might occur?
Quote
JamesD
This is set in motion by the pref "kmeleon.plugins.sessions.cleanShutdown". This is set to false when KM has a good start and reset to true when KM quits. If KM stopped without quitting the pref remains false, This is how KM knows if you had a clean shutdow.
Thanks; I'll have a detailed look at that ...
Quote
JamesD
The last session is the session that was running when KM was last quit. If you quit KM correctly, it will become the previous session when you restart.
Thanks; that's clarified so far ...
Quote
JamesD
However if something went wrong and KM could not shut down correctly, you will get a message upon restarting KM asking if you want to try to use the 'last' session. If you answer yes, KM will start with the last session.
What happens if you first say no? Are you then asked as second question if you want to open the previous session? Sorry that I ask that; I never did so far.
Quote
siria
But it sure could use a less confusing name
Or a little "Help" info in the sessions menu...
I'd really suggest a less confusing name! As I just was thinking it could be the other way round; that the "last" session would be the "last official (correctly closed)" session, and the previous session that one that really was open before (correctly or crashed) closing of the program.
Quote
siria
Awhile ago someone had explained the "last" is actually the "current" session, that hits it exactly - technically. It's true, the current session is continually saved as "last" session. Until next browser start when it's renamed to "previous", and a new "last" one started. One could also reason that after a crash, basically the "interrupted current" session can be continued.
Hmm ... it should not be named "last"; as I consider "last" to be more "last correctly closed" session than "previous running session" (that was active before quitting or crashing the prog). Computing terminology sometimes really can be confusing ...
There are several possibilities to name these two sessions; and I fear that one single word might be confusing. Maybe "uncrashed session" and "interrupted session" might do it, but even that might sound strange and be a bit confusing; "last correctly closed session" would be better but seem quite strange for a user (almost) that never sees crashing the program ...
It might be best to open an official discussion how these two sessions could be named best for future realeases ...