Now that USBstiks have become cost-effective: installations like TinyCore & slax will be increasingly used. Laptops are replacing PCs. These RAM-resident installations give me problems saving the setup, between boots. How are other mc users managing ?
On Thu, Nov 21, 2019 at 4:01 AM <mc-requ...@gnome.org> wrote: > Send mc mailing list submissions to > mc@gnome.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.gnome.org/mailman/listinfo/mc > or, via email, send a message with subject or body 'help' to > mc-requ...@gnome.org > > You can reach the person managing the list at > mc-ow...@gnome.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mc digest..." > > > Today's Topics: > > 1. Merging local and global options (J?rgen Weber) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 21 Nov 2019 09:55:55 +0100 > From: J?rgen Weber <juer...@jwi.de> > To: mc@gnome.org > Subject: Merging local and global options > Message-ID: > <CAFNKvH2qsWB528xxr2K-GdxPVbhh_bnddgVbJ9fhoKO=- > yu...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > 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 > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > mc mailing list > https://mail.gnome.org/mailman/listinfo/mc > > > ------------------------------ > > End of mc Digest, Vol 176, Issue 3 > ********************************** >
_______________________________________________ mc mailing list https://mail.gnome.org/mailman/listinfo/mc
