Fix formatting in the docs for std::process::Command::envs()

[s3rvac]

An empty line between the Basic usage: text and the example is required to properly format the code. Without the empty line, the example is not formatted as code.

Here you can see the current (improper) formatting.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[alexcrichton]

The travis failure looks like it may not be spurious?

[steveklabnik]

@alexcrichton .... uh oh.

Good thing standard style is to put these lines in, and now that we've switched to CommonMark, the old way won't be rendered properly, so this should shake out? But yeah that's not good.

[steveklabnik]

r=me if travis passes

thanks @s3rvac !

[alexcrichton]

@bors: r=steveklabnik

[bors]

📌 Commit 432673a has been approved by steveklabnik

[s3rvac]

@alexcrichton Looks like that the person who originally wrote the example forgot to include the feature attribute. Now that the example is being properly parsed, this resulted in a failure. I have added the missing attribute to the example in commit 432673a. Hopefully, this will fix the tests.

[s3rvac]

This time it looks like a spurious fail that has nothing to do with the PR:

The command "eval git fetch origin +refs/pull/40794/merge: " failed 3 times.