Bug #667
Buffer concept unclear to the user
0%
Description
When hiding or deleting buffers, the difference is not clear to the user.
Which cases cause dataloss?, How do I get hidden buffers back? When do they pop back up automatically?
This could be addressed by merging the concepts. What the user really wants is:
- hiding (get rid of unused buffers from the UI)
- cleanup (get rid of logfiles for privacy reasons, or to save diskspace)
Hiding could be implemented pretty much like it works now
Cleanup could be done manually (Delete History) or automatically by means of a cache policy (Keep at least 500 lines or the last three days of log, for example).
EgS proposed a "hot list", that sounds useful provided:
- it always display channels I've joined
- it display all new queries (wether they're new buffers or just have unread messages)
- it doesn't hide queries immediately, but for example after a day or so (I often refer to inactive queries shortly after the conversation)
History
#1 Updated by EgS over 15 years ago
sebas wrote:
This could be addressed by merging the concepts. What the user really wants is:
- hiding (get rid of unused buffers from the UI)
- cleanup (get rid of logfiles for privacy reasons, or to save diskspace)
I think those 2 options doesn't suffice: The reason for the "hide permanently" is basically to ensure that this buffer will never show up in that specific view. This is of course only helpfull in a multi view concept, but that's exactly it's usecase. Any comments on that?
An example:
I use reduced views when I'm using Quassel on my Maemo n810 or when I'm busy and only want to see important messages.
#2 Updated by johu over 14 years ago
- Status changed from New to Resolved
- Target version set to 0.5.0