Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.3 OS: Linux in CVS HEAD (prior to 3.2), using the "new session" shortcut (either the keyboard shortcut or the session menu button) always opens the default session, while in the past it used to open the same session as was last opened. I really liked that behavior and it would be nice to have this configurable (default to "off" of course) This is the reverse from Bug 57449 , Bug 46685 and possibly Bug 29818 and Bug 29481 . I'm not saying to reverse the bug fixes - just have it configurable. Thanks
With the latest CVS/HEAD (3.4 beta1), the 'new session' opens up the last opened session (which I really dislike). I preferred having 'new session' open the 'default' session, which is what 'Save as Default' meant I thought. The problem with the current system, there is no way to get a 'Save as Default' new session if you've been playing around with the Settings...
I wasn't aware of this being the case in 3.4beta1, but if it is so - YAY :-) I like this option (though it seems confusing at times), but I wouldn't mind it not being the default behavior if it can be configured to behave as I want. As for "Save as default", this saves any settings other then "schema" and "session" as the default for new konsole windows. The default session is always "Shell" for new windows, and the schema is what you last used with the session you chose.
I would also love to have this one configurable, and I am also fine with 'Shell' being the default. I tend to use my laptop as an xterm to many development machines, and got used to the behavior of opening a konsole for each machine that I was working on. Whenever I needed another term, it was just a keyboard shortcut away. Now, however, I have to reach for the mouse, find the new shell button, start a drag action, look at the other tabs to see which host I'm on, and then select that host again. Since I usually like to open three terms at a time, this list of actions has to be repeated three times. It's been over a year since the change, and I'm still having trouble with it.
KDE 4 allows keyboard shortcuts to be defined for each profile, which solves the basic problem here that creating a new shell from a profile other than the default required mouse usage.