Allow minimal config file with runtime defaults

[deckstose]

Is your feature request related to a problem? Please describe.

Right now btop will write a complete config file to disk any time the app is closed.

This makes managing configs with source control tools harder and the config file less comprehensible for humans.

Describe the solution you'd like

It should be possible to only track changes in the config file.

[aristocratos]

This makes managing configs with source control tools harder

Not really, once the file has been pushed once you would only see the diffing lines.

less comprehensible for humans

How so? Every line is commented and since you already have all possible options in the file, you know exactly what can be changed via the config file.

[nickjj]

Just throwing this out there:

Pros of a minimal config

One benefit of a minimal config with only the changes is it's explicit on what you customized.

It means your config can be 1 line if you changed 1 option instead of 250 lines with everything.

It's especially nice for sharing dotfiles because then folks can see "oh, these 3 options are defined, it's likely what's different vs the defaults" instead of "this whole config is here, I wonder what's different vs the defaults". To find out what's different would require someone to install btop, run btop --default-config and then compare it against the dotfiles. That workflow is fine for the dotfiles creator but it could be tedious for someone just poking around.

Cons of a minimal config

It's nice to know what you see what you get. Anything in the config file is active with no need to search for what something is elsewhere.

Which one?

IMO with btop --default-config existing, the pros outweigh the cons.

What do you think?

[deckstose]

Not really, once the file has been pushed once you would only see the diffing lines.

Yeah that wasn't formulated properly, I meant what @nickjj was saying above.