Havoc Pennington

what is reasonable though? I'm not sure of the use cases. maybe if we list some here we could guess. Those implementations you linked above don't do what I expected...

yes, you're right, reading too quickly.

Hmm. Trying to think of the way to enable this with the least API surface. It seems like the minimum is to allow specifying an origin when creating a ConfigValue...

http://typesafehub.github.io/config/latest/api/com/typesafe/config/ConfigIncluder.html exists, but I don't have a good example to point to. The general outline of how this works is that you set an includer on your ConfigParseOptions, then the...

That looks right to me. If you wanted to chain to the regular default includer, you would add a field `ConfigIncluder fallback`, then in withFallback you copy your includer but...

https://github.com/typesafehub/config/blob/master/HOCON.md#include-semantics-locating-resources is how it's supposed to work (maybe it even does!) Yes, foo.conf is supposed to be found relative to the file that included foo.conf. I apologize for not catching...

I added PR #277 which tests and documents the current behavior. Right now only the "heuristic" includes (without file()) do the "look adjacent" trick. I think we should probably change...

No idea offhand. I guess you are trying a thing like `include "../foo.conf"` ? I don't think there's a test case for that in the test suite, I don't know...

yyy can't be both a boolean value and also an object that contains another boolean value. a.b=true is a shorthand for a:{b:true} "a.b"=true is shorthand for {"a.b":true} (see the discussion...

HOCON is a json superset so you can still write that syntax in the file if you want. Most of the API takes path expressions,`a.b` means two keys unless you...