Version: r893349 (using Devel) Compiler: g++ (Ubuntu 4.3.2-1ubuntu11) 4.3.2 OS: Linux Installed from: Compiled sources Kate fails to remember the following things after I close and restart it: - whether the Tab Bar Extension is loaded - whether the OpenHeader plugin is loaded - whether Documents or Filesystem Browser sidebars are open - which directory the Filesystem Browser was last in - whether the Filesystem Browser was using icons or detailed view In fact, it doesn't seem to remember which plugins are loaded at all -- the above (and I assume others) are always disabled, while some (filesystem browser, terminal toolview, find in files toolview) are always enabled at start even if I disable them. However, it remembers other settings from the config dialog, along with the settings for the Tab Bar Extension itself. "Include window configuration" in Settings -> Sessions is enabled.
If you use sessions it should work out of the box. Try Sessions > Save as Default Session. Does that help?
Is this a copy of something? This is because I never got to commit the changes of the default session concept at the Kate developer sprint. I'm planning to get this patch back in shape for trunk during christmas.
If I do Sessions -> Save As Default..., it remembers the settings I had changed up till then, but not anything I change afterwards. I guess this is Good Enough so that I don't have to keep reenabling the tab bar extension every time. Thanks. It would be nice if the filesystem browser were to remember its last location, though. I have "start new session" and "do not save session" set in the settings, assuming these control storing/restoring which documents are open, which I don't want. (It's not clear to me what certain combinations of these, such as "load last session" along with "do not save session", or "start new session" along with "save session" would do...)
For 4.2, - Keybindings (save, open, document quick switch) other than the katepart keybindings (katepart keybindings = move to end of line, etc.). I think I got a few things to work when I deleted the default scheme (click "details >>" on the bottom of the bar), but it was so unusable (no ctrl+s, etc.) that I switched back.
I'm on Ubuntu 9.04 Jaunty, and it seems to me that any changes made to Kate's configuration are written into ~/.kde/share/config/katerc, but Kate always loads its configuration on startup from /usr/share/kde4/apps/kate/default.katesession. The "set as default session" fixed the problem for me, but the default behavior of writing settings to one file and reading them from another seems counterintuitive to me.
I confirm the same behaviour in Kubuntu Karmic with KDE 4.3.3.
*** This bug has been marked as a duplicate of bug 156330 ***