Make the shell snippets easier to copy/paste (e.g. cargo/running-locally.md)? about comprehensive-rust

[mgeisler]

Yeah, that's definitely an annoyance. It's reported upstream here: rust-lang/mdBook#864.

People tried to fix it repeatedly: #25 and #29. So we should probably do something about it...

My idea would be to fix it upstream, but I haven't taken the time to do that.

[mgeisler]

Fixed via #951.

[sharunkumar]

We could separate the output from the shell commands (like you did in your PRs)

@mgeisler when doing this, the test build fails on the PR

I noticed this when I tried it in the previous PR itself, not sure how to fix it

Update: figured it out, had to specify the language for the new code block

[gendx]

Glad to see it's already reported upstream :)

[mgeisler]

Our style guide actually talks about this: https://developers.google.com/style/code-syntax#prompt.

The system used there knows to not copy the $, even for examples that contain multiple commands. I think we should enhance mdbook with a similar capability.

[mgeisler]

If mdbook ever gets support for not copying the prompt, then we can consider adding the prompts back. For now, it's probably better to remove them since this has been suggested repeatedly 😄

[mgeisler]

Hi @sharunkumar, thanks for tackling this. There is a final place where we have a $ infront of the shell commands: build_all.sh. These dollar signs show up in the Android section.

We should fix those too to make things consistent. Right now, we include the commands from the shell script and hard-code the output. So the Markdown on the page linked above looks like this:

```shell
{{#include ../build_all.sh:hello_rust}}
Hello from Rust!
```

We could separate the output from the shell commands (like you did in your PRs).

[sharunkumar]

Oh alright I could check it out

[sharunkumar]

Idk if its because I'm running it from windows but when I run mdbook serve this is what that page looks like on localhost, after the changes:

Update: looks good on WSL though, but not sure why it looks the way it does when serving from windows 🤔

[mgeisler]

We could separate the output from the shell commands (like you did in your PRs)

@mgeisler when doing this, the test build fails on the PR

I noticed this when I tried it in the previous PR itself, not sure how to fix it

Update: figured it out, had to specify the language for the new code block

Great that you figured it out — the error looks very mysterious at first! 😄