micro-editor / micro-editor/micro
`micro` does not work well with 16bpp framebuffer in `fbterm`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
The default framebuffer set up on a Raspberry Pi with the vc4-kms-v3d overlay boot option is 16bpp, which absolutely breaks fbterm trying to run micro (no editor is displayed and micro apparently seems to fail to load, carriage return is broken causing newlines to fall diagonally and the entire terminal turns useless, basically forcing the user to shut down fbterm to recover usability). This occurs when echo $TERM gives fbterm, but micro works fine when it's set to other values (such as linux or xterm-mono)
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the issue on a Raspberry Pi using the vc4-kms-v3d overlay, with TERM set to fbterm, and compare it with linux or xterm-mono. Done means micro displays correctly in fbterm, carriage returns produce normal newlines, and the terminal remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux, raspberry-pi
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100