Ryan Leckey

Yeah.. I definitely want this as there are lot of use cases that could benefit. Here is the API in my head: ```rust c.merge(File::with_name("Settings")); c.get("key"); //= 1 c.watch(|| { //...

This is now _possible_ ( check out https://github.com/mehcode/config-rs/blob/master/examples/watch/src/main.rs ) A couple more questions to answer before `.watch` should be added. 1. Is `Config.watch` stating that we are watching _all_ sources?...

This is #57 --- Sadly there isn't an easy way to fix this with the current architecture. I'm aiming at changing that in `0.10` which I'm currently spiking out as...

:bowing_man: Thank you for your contribution. I apologize for the late response. Moving forward I want to re-think the design of config as a whole. See #111 for more details....

I agree. Thanks for the suggestion.

This is not a feature I'm looking at implementing in the near future but I'm definitely open to the idea. With the merging it'd require a bit of thinking on...

Looking back at this, I'm thinking we could implement _something_ that would work for enough use cases to be useful. I looked around and it seems there are two common...

There are two main use cases at play: - Write back changes to a loaded config file. Think Atom/VS Code. App loads from multiple sources and writes back only dynamic...

Apologies for the time lost. What specific use case were you wanting to do?

A close integration with clap would definitely be a neat thing to have.