It might forget them because it segfaults on exit, or says "QThreadStorage: Thread 0x9cfeb48 exited after QThreadStorage 2147483641 destroyed".
Bug? http://bugs.kde.org/show_bug.cgi?id=171276 says feature - "either you want to have the list of
recently opened files stored, which is done in the session, or you don't."
I don't know what to make of that. Yes, if I work with sessions, the "Open recent" submenu (of the "File" menu) becomes populated.
But I work with sessions to open a number of very specific files, not simply to have a recent file list! In fact, I want a recent file list for those situations where I don't have the desired bunch of files open alredy!
Right now it seems that the only way to maintain a half-way normal recent file list would be to (1) always start with some default session, (2) make sure you close all open files again when you're done, (3) save the now-empty session only for the sake of its recent file list.
A bit complicated. Is that really not a bug?
Bug? http://bugs.kde.org/show_bug.cgi?id=171276 says feature - "either you want to have the list of
recently opened files stored, which is done in the session, or you don't."
I don't know what to make of that. Yes, if I work with sessions, the "Open recent" submenu (of the "File" menu) becomes populated.
But I work with sessions to open a number of very specific files, not simply to have a recent file list! In fact, I want a recent file list for those situations where I don't have the desired bunch of files open alredy!
Right now it seems that the only way to maintain a half-way normal recent file list would be to (1) always start with some default session, (2) make sure you close all open files again when you're done, (3) save the now-empty session only for the sake of its recent file list.
A bit complicated. Is that really not a bug?
Comment