Project

General

Profile

Feature #619

Introduce BufferConfig - persistent per-buffer attributes

Added by Sputnick almost 13 years ago. Updated almost 13 years ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/12/2009
Due date:
% Done:

0%

Estimated time:
OS:
Any

Description

There are some data we'd like to set and store for each buffer separately:

- Encoding (such that some buffers can have a different fallback than the default)
- Session restore behavior: Always join/Never join/Restore last state
- Buffer-specific ignore and highlight lists
- Possibly more once we start thinking about that

So we'd need BufferConfig object that is synced, and a way to store attributes coupled to BufferId in the database. Personally I'd like a flexible approach, e.g. serializing BufferConfig via QVariant, so we can easily add new features, and don't keep a ton of empty fields in the database (only settings differing from the default would be stored).

One could access such settings via right-click on a buffer item, for example.

History

#1 Updated by pennywise almost 13 years ago

- chatline input history should be also per buffer instead of global

#2 Updated by TerrorBite almost 13 years ago

pennywise wrote:

- chatline input history should be also per buffer instead of global

I agree with this. Possibly the input box itself should also be per-buffer but I know that some people like having it global

#3 Updated by EgS almost 13 years ago

yes, but that's a different BR. I always forget the id, but there is one.
This BR is regarding persistent stuff, which is more like buffer specific settings which should survive a core restart.

Also available in: Atom PDF