micro-editor / micro-editor/micro
Truecolor not supported by Micro's built-in terminal emulator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
In terminal apps (like ghostty and iterm2) that support truecolor (and that set COLORTERM=truecolor by default), and with MICRO_TRUECOLOR=1, micro's built-in terminal emulator does not appear to support truecolor itself.
UPDATE Ah, I see that micro depends on a fork of james4k/terminal which AFAIK has no truecolor support itself at the moment. Seems like a fair bit of work to get there...
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 tracing micro’s built-in terminal emulator and its fork of james4k/terminal, focusing on how COLORTERM=truecolor and MICRO_TRUECOLOR=1 affect color handling. Confirm the current terminal color path and identify the scope needed for truecolor support. Done means the built-in emulator renders truecolor correctly in the stated terminal environments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100