The cargo reference should mention how to control number of jobs via env

[gnzlbg]

The environment variables section of the cargo reference does not mention how to control the number of jobs for cargo via an environment variable. It should.

https://doc.rust-lang.org/cargo/reference/environment-variables.html

[zachlute]

There is a link at the bottom of the "Environment Variables Cargo reads" section that states:

Note that Cargo will also read environment variables for .cargo/config configuration values, as described in that documentation

The documentation at that link says:

Cargo can also be configured through environment variables in addition to the TOML syntax above. For each configuration key above of the form foo.bar the environment variable CARGO_FOO_BAR can also be used to define the value. For example the build.jobs key can also be defined by CARGO_BUILD_JOBS.

So I guess the question is, does it make sense to specifically call out things you'd commonly use as "Environment Variables Cargo reads" for more discoverability, or to remain consistent and have all of the config-override variables handled the same?

[gnzlbg]

So I guess the question is, does it make sense to specifically call out things you'd commonly use as "Environment Variables Cargo reads" for more discoverability, or to remain consistent and have all of the config-override variables handled the same?

I often end up trying to find documentation in both of these places, and for me it would make sense if the list of environment variable was more "comprehensive" and cross-linked with the configuration keys.

I am not suggesting that these should be generated and kept in sync manually. But maybe it would be good to explore automatically generating a part of the environment variable list from the keys.

[zachlute]

#5690 appears to be asking for essentially the same thing, FWIW. It's clear there could be some improvement in discoverability here.