Skip to content

feat: Allow --config strings in sketch.yaml (esp. baudrate) #2640

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
3 tasks done
egnor opened this issue Jun 17, 2024 · 0 comments · Fixed by #2717
Closed
3 tasks done

feat: Allow --config strings in sketch.yaml (esp. baudrate) #2640

egnor opened this issue Jun 17, 2024 · 0 comments · Fixed by #2717
Assignees
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement

Comments

@egnor
Copy link

egnor commented Jun 17, 2024

Describe the request

It would be nice if sketch.yaml let one specify the default baudrate for arduino-cli monitor, as 9600 baud is v...e...r...y...s...l...o...w... and typing -c baudrate=115200 gets old. Obviously I can make a script wrapper or alias or something but I feel like this kind of thing is what profiles are all about.

(Per #2554 this should probably be per-profile, not sketch-global.)

Describe the current behavior

There's no (obvious) way to specify serial monitor baud rate (or other communications port properties) except on the command line.

Arduino CLI version

1.0.0

Operating system

Linux, N/A

Operating system version

(true in all OS)

Additional context

No response

Issue checklist

  • I searched for previous requests in the issue tracker
  • I verified the feature was still missing when using the nightly build
  • My request contains all necessary details
@egnor egnor added the type: enhancement Proposed improvement label Jun 17, 2024
@per1234 per1234 added the topic: code Related to content of the project itself label Jun 17, 2024
@cmaglie cmaglie self-assigned this Oct 4, 2024
@cmaglie cmaglie added this to the Arduino CLI v1.1.0 milestone Oct 4, 2024
@per1234 per1234 added the conclusion: resolved Issue was resolved label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conclusion: resolved Issue was resolved topic: code Related to content of the project itself type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants