This is a great idea. I feel that the best total situation is 2 things: 1. A way to print the paths to all files visible that will be read for configuration. T

This is a great idea. I feel that the best total situation is 2 things: 1. A way to print the paths to all files visible that will be read for configuration. This means that if the user config file means the system config file is ignored, print only the user config file path. Alternatively print that the system file will not be read but show its path anyways. There's many ways to solve this and it depends on the way the app loads configs. 2. A way to print the final configuration after it's been loaded and validated. This should show what settings override others. For example if the user misunderstands the config merging or erroneously quotes a numeric value causing validation to fail, this would be a great way to triangulate that. I've seen quite a few apps implement #2 but rarely do they have #1.