Version: nieznana (using KDE 3.1.4) Installed from: Gentoo Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice) OS: Linux (i686) release 2.4.23 An option (in open/save dialogs) not to remember opened files (in recent documents in kde menu) would be useful to keep clutter (such as mp3s/oggs) out of that menu option. As it is now the menu is hardly useful at all to people often changing playlist contents (like me) --- often the only files listed in ``recent documents'' are media files, and these are more often than not found and opened through the dialogs. Ideally, the state of this option would be remembered per-application (with a default and override settable through kcontrol), just like the left-hand quick-access icons (or whatever it is called) are; so that I could disable remembering these in splitplaylist and finally have a useful recent documents menu.
Moving from "kio/kfile" component to "kfile" product, helps sorting out duplicates.
macOS has a global toggle for this. Maybe we should too.
Isn't that what the "private" activity is for?
I suppose so, but a dedicated "privacy mode" is a heavyweight solution; not everyone wants to use Activities. Also it's not very discoverable.
>would be useful to keep clutter (such as mp3s/oggs) out of that menu option. but then instead of clutter you have a blank space. That's even less useful
That way this would probably work is then when you've globally turned off the recent document feature, the menu item would become disabled rather than show a dumb blank list.
Related: Bug 355399. Probably we could implement this by allowing the requested global value to be set to zero (that's not how we would have to implement it in the UI though; we could have a nice set of radio buttons).
In fact this option already exists in the Activities KCM: System Settings > Workspace Behavior > Activities > Privacy > Do Not Remember The problem is, this is pretty un-discoverable. I don't think most people would guess that the setting lives on the Activities page. That's a UI issue though that we'll track separately with Bug 416271.
*** This bug has been marked as a duplicate of bug 416271 ***