Valentin Gagarin

@aschmolck Really sorry that your PR has been hanging around for so long. Are you still interested in merging this? If so, could you please rebase?

> doxygen @edolstra Do we have infrastructure to make this visible on a par with the manual? As long as we don't, I'm strongly in favor of adding this type...

> People have a bias "programing language = implementation", so we are simply laundering the exact same information in a format that seems more "platonic". @Ericson2314 when we worked on...

@amjoseph-nixpkgs I agree on stopping the hard-wrapping, and have a [pull request for the nix.dev contribution guide](https://github.com/NixOS/nix.dev/pull/261/files#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055R170), which is the [central place to coordinate documentation work](https://github.com/NixOS/nix.dev/issues/285#issuecomment-1177939217) and should (in the...

@Ericson2314 Then what about we consistently use *substituter* (is that even properly translated from Latin into English? shouldn't it be *substitutor*?) and collapse the notes here into one?

> This distinction isn't just internal to the codebase; it has leaked out onto user-facing surfaces. From the perspective of trying to present a sane interface in documentation, I think...

@thufschmitt We can still have links in the HTML rendering. @whentze are you still interested in pursuing this this? Documentation of configuration options is not great right now, and your...

I agree with the concern, and can only add my observations: - progress is proportional to time spent - we start way more things than we finish (which is in...

Discussed in the Nix team meeting: - @edolstra: constraints: as little configuration as possible, also efficiency - @thufschmitt: we may fail somewhat gracefully when input-addressed paths cannot be pushed -...

@aschmolck nice! I agree with @Ericson2314 though that we should merge the large manual PR first.