stty: support B460800 and B921600 baud rates
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- cli, operating-systems
Research direction
Start at the stty implementation and inspect its existing baud-rate mapping. Verify that nix::sys::termios exposes B460800 and B921600 after nix pull request 2815 lands, then map 460800 and 921600 to those constants. Done means both rates are accepted where the platform provides them.
Written by the indexing model from the issue text.
Description
stty should support the 460800 and 921600 baud rates.
This currently depends on https://github.com/nix-rust/nix/pull/2815, which adds B460800 and B921600 to nix::sys::termios on platforms where libc provides them.
Once that lands, uutils should map:
460800→B460800921600→B921600
- Dominant language
- Rust
- Stars
- 24.2k
- Forks
- 2.1k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 324
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
minorbug(mv): invalid mode errors not quotedPossibly taken @henrimarconni claimed this 1 day ago. OpenU - mv
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ptx: break file missing path in error messagePossibly taken @Franklin-Qi claimed this 1 day ago. OpenU - ptx
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
uutils/coreutils#15307 · 1 comment ·
Maintainers usually reply within 1 day
-
minorbug(stat): os errno not stripped when failing to flush stdoutPossibly taken @cestercian claimed this 8 days ago. OpenU - stat
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
uutils/coreutils#15200 · 3 comments ·
Maintainers usually reply within 1 day
-
B - high priority U - du
Difficulty 1/5 Under an hour Newbie friendliness 82/100
uutils/coreutils#14984 · 1 comment ·
Maintainers usually reply within 1 day
-
hostname: when domain is none, it should be outputted to stdoutPossibly taken A pull request linked to this issue is open or already merged. OpenU - hostname
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uutils/coreutils#14962 · 3 comments ·
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
shep-pm/shep-kelpie#980 ·
Maintainers usually reply within 1 day
-
bug frontend rt sev-3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
C-bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
[1.x Bug] run-operation --sql reports success but rolls back writes on transaction-capable adaptersOpentriage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
dbt-labs/dbt#16784 · 1 comment ·
Maintainers usually reply within 1 day
-
area:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day