adding example usage for command option

[TZubiri]

Hello, please take a look at this small documentation change.

Basically I struggled for a while to figure out why the monitor wasn't working, and I had to play with the IDE to understand that I needed to match the baud rates.

I'm adding a really low effort change that might help users work out how to use the -c option once they figured out they need to change the baud rate.

Ideally I think the options should be collapsed into command line flags so that the following works:

arduino-cli monitor --baudrate 1000000

But for now I think this small change can be pulled, if it can be tested by someone with a working build.

If possible, I would also change the flag usage from

-c, --config strings

to

-c --config ID=Setting

in addition to clarifying the syntax, it also points the user towards the --describe keywords.

Thank you.
Tom

[CLAassistant]

All committers have signed the CLA.

[per1234]

Thanks for your contribution @TZubiri.

This file is automatically generated so it can not be edited directly. You must instead edit the source string at the path and line indicated by the comment:

arduino-cli/i18n/data/en.po

Line 415 in c52fcf8

#: cli/monitor/monitor.go:63

here:

arduino-cli/cli/monitor/monitor.go

Line 63 in c52fcf8

monitorCommand.Flags().StringSliceVarP(&configs, "config", "c", []string{}, tr("Configuration of the port."))

Any edits made to this en.po file would only be overwritten by the automated system on the next sync.

I have submitted a proposal to more effectively communicate this fact to contributors: #1837
I welcome any feedback you might have on that proposal, so feel free to review that PR