support for invalid UTF-8 bytes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
Research direction
Start with the String- and spacing-related code linked in src/uu/ls/src/ls.rs, then inspect how uutils-term-grid represents and renders cell content. Compare the proposed [u8], OsStr(ing), and AsRef API options. Done means grid output can preserve and display invalid UTF-8 byte sequences for the affected ls option combinations.
Written by the indexing model from the issue text.
Description
There are some combinations of options that require ls to display non-UTF-8 byte sequences in a grid. Because this crate only supports String (and spaces), this isn't currently possible. Support should be added for invalid UTF-8 somehow, accepting one of &[u8], OsStr(ing), or AsRef<OsStr>.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 13
- Avg merge
- 11h 54m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/uutils-term-grid
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
uutils/uutils-term-grid#45 · 2 comments ·
-
Dependency DashboardOpen
Difficulty 4/5 3-5 days Newbie friendliness 15/100
uutils/uutils-term-grid#13 ·
All issues in uutils/uutils-term-grid
Similar issues
-
bug easy good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lacs-project/sysknife#659 ·
Maintainers usually reply within 2 days
-
E_FIT_INPUT_MISSING (mixture overrides): the message says ferx-r bundles lack mixture_overridesOpenP3
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#2431 ·
Maintainers usually reply within 1 day
-
contribution
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
farion1231/cc-switch#8863 · 1 comment ·
Maintainers usually reply within 1 day