torvalds/uemacs

Random version of microemacs with my private modificatons

View on GitHub ↗Jump to charts ↓

torvalds/uemacs has 2k+ stars and 300+ forks on GitHub, is written in C, and was last pushed on Aug 6, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:ApplicationCategory(s):Editors & IDEsDeveloper Tools
Added to GitGenius on October 13th, 2026
Created on January 17th, 2018
Open Issues & Pull Requests: 17 (+0)
GitHub issues: Enabled
Number of forks: 325
Total Stargazers: 2,170 (+0)
Total Subscribers: 63 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.8 days
Mean response time: 249.5 days
90th percentile: 853.9 days
Tracked items: 17

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 205 days
Stale 30+ days: 3
Stale 90+ days: 3

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The tool addresses the narrow use case of preserving muscle memory for a developer who has used this specific editor since the 1980s. It operates as a legacy editor designed for severely constrained hardware environments, with keybindings that diverge significantly from standard Emacs and are incompatible with modern editor conventions. The README explicitly discourages adoption, stating the editor is poorly maintained and unsuitable for new users.

Adoption is not recommended for any project or developer except those with decades of accumulated experience using this exact version. The tool's keybindings are intentionally non-standard and cannot be easily retrained away from. The README names no alternatives and makes no comparisons to other editors, instead advising potential users to choose something else entirely. The project exists solely because its maintainer cannot retrain their fingers from its unusual key mappings.

Development activity is minimal and reactive. The project receives only occasional updates to keep it functioning in modern environments, with no active feature development or modernization efforts. The codebase remains rooted in design decisions made for 1980s hardware constraints and has not been substantially reimagined for contemporary use.