Don't write options to disk when they're at their default values about weechat HOT 15 OPEN

@kutsan use autoconf.py

from weechat.

i'd also like something like this (or an rc file). Since i like to manage all of my systems via ansible and automate setup after I wipe a machine, it would be nice to have a way to configure only what I want changed from the defaults. This would make the changes to the config files in git more meaningful.

from weechat.

One way to attack this would be to have some sort of config include/merging mechanism. Have basic set of configs in /usr/share, then /etc, then ~/.weechat. /save would always only touch the home file. (This would also solve #775)

from weechat.

+1. I'm glad this is a task/issue:

75 options with value changed
$ cat *.conf|wc -l
1285

from weechat.

I like this, maybe a command that would show out-of-date options too?

Like for 0.4.4 weechat.look.hotlist_add_conditions replaces weechat.look.hotlist_add_buffer_if_away

So something like /depreciated would print:
setting: <setting> replaced by <setting>

So you could manually /unset the first and /set on the second if you wished to change it from the default behavior?

from weechat.

@shawn-smith: the obsolete options are displayed only once at startup. The old name does not even exist in WeeChat (it's just read one time in file and discarded), so it's not possible later to display obsolete options.
This document shows the manual actions required when you upgrade to a newer version (almost everything in WeeChat is automatic when upgrading): http://weechat.org/files/releasenotes/ReleaseNotes-devel.html (file ReleaseNotes.asciidoc in git).

from weechat.

Oh I was unaware of this, I haven't had to update yet.

Disregard what I said then lol

from weechat.

Any current status on this? This would make version-controlling much easier!

It also solves a big problem where users of version X are stuck with version X defaults, as detailed here. This may be okay as a default, but it would be quite nice to allow some users to specify that they want their configurations to change as new defaults change.

Googlers: I've since made a wrapper script that detects and writes only changed configuration values.

from weechat.

Just a friendly reminder that this would be a really helpful addition to weechat. Easy version-controlling of changes is likely to be important to a lot of people.

from weechat.

Just realized that weechat writes out the config files in somewhat random orders on each /save. This makes them incredibly nasty to version, and makes the ability to provide user overrides of config files even more important.

EDIT: Not actually sure if this is right? I'm having trouble reproducing it. If I can't then versioning all of .weechat except for logs and weechat.log should be a pretty good solution.

from weechat.

The order of config files is not random, they are "sorted" by time of load, so WeeChat should load in this order:

1. sec.conf (which is loaded before all other config files)
2. weechat.conf
3. plugins config files, depending on the priority of each plugin (used to load plugins in order, see API doc for more info: https://weechat.org/files/doc/devel/weechat_plugin_api.en.html#plugin_priority).

from weechat.

@flashcode: Thanks! But I meant that the options within each config were getting written out in different orders. Since then I haven't been able to reproduce it though, so that part's not an issue for me anymore.

from weechat.

Since after 3 years, what's the current status of this issue?

from weechat.

@kutsan: Nothing from the weechat team, but you can use a wrapper script I wrote to detect config changes and only write what has changed since the default.

from weechat.

@qguv That's cool. I didn't see it earlier, thanks.

from weechat.