Adding quotes to large command base inputs

[dggaytan]

What does this PR do?

Before submitting

• [✅] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• [✅] Did you read the contributor guideline, Pull Request section?
• [ ] Was this discussed/approved via a Github issue or the forum? Please add a link to it if that's the case.
• [ ] Did you make sure to update the documentation with your changes? Here are the documentation guidelines, and here are tips on formatting docstrings.
• [ ] Did you write any new necessary tests?

cc: @ArthurZucker

[Rocketknight1]

Hi @dggaytan, what's the reason for this change?

[dggaytan]

Hi @dggaytan, what's the reason for this change?

Improve usability, I was testing this example for XPU and since the example itself is kind of heavy, this simple change can avoid interruptions while running as the readme says.

[Rocketknight1]

I'm not sure I understand! It seems like the usability is identical to me

[dggaytan]

Yes, so when I was copying and pasting the commands as it is in the readme, the large run command was not working as it should, and found out that when I added the quotes for the input values it worked fine

[Rocketknight1]

Interesting - are you running on Windows?

[dggaytan]

on linux, ubuntu 22.04

[Rocketknight1]

Hmm! I would have expected both commands to work the same, at least in common Linux shells. cc @sunmarc does accelerate expect input args to be quoted?

[dggaytan]

Hmm! I would have expected both commands to work the same, at least in common Linux shells. cc @SunMarc does accelerate expect input args to be quoted?

Hi there, realized there was an extra space at the beginning of the command so the rest of passing inputs wasn't being read correctly, quotes actually does not affect at all in numerical values

[Rocketknight1]

That makes sense! Can we close the PR, in that case?

[dggaytan]

That makes sense! Can we close the PR, in that case?

The extra space appears in the readme from the main branch, I'm not sure how you handle this type of details (typos). 🤔

[Rocketknight1]

Oh, I understand now! There's a space after the \ on the first line, which means that we don't escape the newline correctly. That makes sense! Can you rework this PR so that you leave everything else the same, but just delete that extra space? That should resolve the issue I think.

[dggaytan]

Oh, I understand now! There's a space after the \ on the first line, which means that we don't escape the newline correctly. That makes sense! Can you rework this PR so that you leave everything else the same, but just delete that extra space? That should resolve the issue I think.

Hi there, sorry for the late review, I think is all set now :) Let me know if there are some other changes needed

thanks

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.