Thank you for continuing the discussion! Sorry for my delayed response while I was out for C meetings.
+1, I think respecting line directives will match user expectations best.
Thanks! I think that’s a good direction as well.
I’m still concerned about using yet another custom format for configuration. IMO, it’s better to pick one style and use it consistently so that users don’t have to go searching for documentation on what features use which formats. I definitely don’t see an argument that one is more readable than the other – both are textual formats, both are intentionally human-readable, and at least JSON is designed to be modified in backwards compatible ways in a more straightforward fashion. It’s not that we can’t find a way to augment the other format, but I don’t see why we should make that harder by making us think up more complex syntax either.
That said, I won’t block the RFC over it.
+1