micro-editor / micro-editor/micro
Huge input lag when browsing through code on RPi B+ v1.2 in console mode [Nano is much faster]
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
Description of the problem or steps to reproduce
Input lag with keyboard (compared to Nano 5.4) is atrocious (nearly unusable). Simply pressing the arrow keys to navigate through the code is a painful experience with micro (which I deeply love 😢).
Specifications
Using micro 2.0.8 on a recently dusted Raspberry Pi B+ v1.2 (yes, one of the old ones) in console mode ONLY (no desktop to save resources).
Tested with the codebase from the picalc-chudnovsky repo.
Nano editor lag:
https://github.com/zyedidia/micro/assets/3759916/c123daf3-fd2b-43a3-ba17-892415294f3c
Micro editor lag (lifting my figers to show the lag after pressing arrow-down):
https://github.com/zyedidia/micro/assets/3759916/1bd2fc10-d8a6-4564-9ee2-374b36c8eb63
Commit hash: 2.0.8
OS: Raspbian 11
(Linux 6.1.21+)
Terminal: Native
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
Reproduce the lag in console mode on the stated Raspberry Pi B+ hardware using the picalc-chudnovsky codebase and compare arrow-key navigation with Nano. Start by tracing the console-mode input path and measure responsiveness; done means identifying the bottleneck and confirming that navigation is substantially less laggy on the reported setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100