Merging local and global options
Yury V. Zaytsev
yury at shurup.com
Thu Nov 21 21:16:19 UTC 2019
The ticket is waiting for its hero for more than a decade:
https://midnight-commander.org/ticket/1677
Sent from my iPad
> On 21. Nov 2019, at 09:57, Jürgen Weber <juergen at jwi.de> wrote:
>
> Hi,
>
> Currently the user config replaces the global config, so the user
> config has to contain everything instead of only the user adapted
> values.
>
> I think mc's configuration system should be changed so that
> ~/.config/mc/ and /etc/mc/ are merged with the first having
> precedence.
>
> if the user changes an option in the gui, mc would write the changed
> option to the user config.
>
> If the new option value is equal to the one in the (global+compiled
> in) ini, then mc should remove the option from the user ini.
> Old local copies of the global options would therefore be cleaned on saving.
>
> Also, there should be a command line option to show the active (==
> merged) options.
>
> from the current 4.8.22 man page:
> At startup, Midnight Commander tries to load initialization
> information from the ~/.config/mc/ini file. If this file doesn't
> exist, the system-wide file /etc/mc/mc.ini is used. If this
> file doesn't exist, the system-wide file /usr/share/mc/mc.ini is
> used. If this file doesn't exist, MC uses the default settings.
>
> after the change:
> At startup, Midnight Commander loads initialization information
> from the ~/.config/mc/ini file and the system-wide file
> /etc/mc/mc.ini. Options from the former override the system-wide
> options. If an option is not found in either config file, MC uses the
> default settings.
>
>
> What do you think?
>
> Greetings,
> Juergen
> _______________________________________________
> mc mailing list
> https://mail.gnome.org/mailman/listinfo/mc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.midnight-commander.org/pipermail/mc/attachments/20191121/01e1814f/attachment.html>
More information about the mc
mailing list