Summary: | Make recent files list global, rather than per session | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Aneurin Price <aneurin.price> |
Component: | sessions | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | balazs, greg, naught101, oleg.sev, psychonaut, pzcdyhbb0nzq9layi4mcj1hhp, silver.salonen, teuniz, torquil, zonken |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: |
Description
Aneurin Price
2009-02-01 19:04:00 UTC
> I can understand the desire to have the MRU list separate between sessions, but
> what about an exception for the default session?
I think I'd favor for (named) sessions to still had their own MRU, but at least in 'always start new session' mode, I agree there should be /something/.
*** Bug 193043 has been marked as a duplicate of this bug. *** *** Bug 149896 has been marked as a duplicate of this bug. *** Ides on how to solve this: 1. make Recent Files independent of sessions 2. make it an option: either per session or independent 3. save it per session + always add to default session (need to reintroduce a default fixed session) 1. is easiest. But 3. should be best. Thoughts? related: bug #193162 This seems to be a duplicate of Bug 144355. It's related, but does not really matter. The reports are there as this one. It doesn't make much sense to change 144355 to duplicate of this bug. *** Bug 196770 has been marked as a duplicate of this bug. *** + one for option 2. - make it an option: either per session or independent *** Bug 225356 has been marked as a duplicate of this bug. *** *** Bug 228027 has been marked as a duplicate of this bug. *** @Aneurin and all other followers of the bug: I've blogged baout this issue to get a general opinion about whether recent files should be global or per session [1]. It's hard to find a consensus, especially since also users not using sessions give their opinion. For KDE4.6, all the configuration if unnamed/anonymous sessions are saved and reused for new sessions. This includes recent files. In other words: Recent files are still per session, but all unnamed sessions use the same recent-files list (think of not using sessions at all). Question is now: Are you ok with closing this report with this described behavior (still per session; but remembers for unnamed, i.e. kind of global for unnamed sessions)? [1] http://kate-editor.org/2010/10/27/recent-files-menu-in-kate/ To me it sounds OK, but I didn't know I can use "anonymous" sessions :) I have to confess that I haven't tried 4.6, but as described it seems like a sensible way to behave, so I'd consider it 'fixed'. (It's encouraging to see minor issues like this getting solved. Small bugs and wishlist items seem fairly insignificant but add a far more polished feel overall) Thanks for your replies. I'll close the report then. Meanwhile, if you want to try the current behavior for KDE 4.6, just follow http://kate-editor.org/get-it/ |