id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	branch_state	votes
2772	Suggestion to load /etc/mc/mc.ext after ~/.config/mc/mc.ext anyway or add keyword to mc.ext for this purpose.	gavenkoa		"If I create '''~/.config/mc/mc.ext''' then '''/etc/mc/mc.ext''' no longer parsed.

I want to track my personal customization to mc.ext but also I want stay in touch with upstream version of mc.ext.

To use upstream version of '''mc.ext''' with my small but essential for me customizations I need merge these two files:

{{{
  $ cat $skelproj/.config/mc/mc.ext /etc/mc/mc.ext > ~/.config/mc/mc.ext
}}}

Pretty easy but how about '''keyword''' to load system wide configs? So anyone can just copy mc.ext to proper place?"	enhancement	new	major	Future Releases	mc-core	master		hg.ext bindings	gavenkoa@…	1677		no branch