mg

Micro (GNU) Emacs-like text editor ❤️ public-domain

Runssource: GitHubhomepageCUnlicensecommit 7bae32d01051

C, Unlicense licensed. The project labels itself: alpine linux, bsd, cygwin, debian, docker image, dragonfly, dragonflybsd and editor.

mg runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

mg 4.1 builds, installs, answers -h, runs batch mode (exit 0), and a real pty session saved the typed text 'FINAL PROOF' to disk with exit code 0.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
650
forks
66
open issues
1
watchers
18
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing mg, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • autogen.sh fails: autoreconf not found (no autotools in container)8 minutes
  • Link errors: missing fparseln/recallocarray/strtonum and cscope symbols; lib objects lacked -Isrc5 minutes
  • Default curses build cannot compile: /usr/include term.h/curses.h headers absent (no libncurses-dev; cannot apt install without root)2 minutes
Install time
15 minutes
Cold machine to finish
10 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
make exited 0 and produced ./mg; './mg -h' printed usage and exited 0; './mg -b README.md' exited 0; drove real editor over a pty typing 'FINAL PROOF' then C-x C-s: echo line read 'Wrote /tmp/argus-final.txt' and file content was exactly 'FINAL PROOF', then C-x C-c + 'yes' exited 0; make DESTDIR=/tmp/pkg2 install exited 0 and /tmp/pkg2/usr/local/bin/mg -b README.md exited 0
Model tokens used
1,065,006
Exact commit tested
7bae32d01051
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

step1 configure exit: 0
step2 make exit: 0
cc  -o mg obj/basic.o obj/bell.o obj/buffer.o obj/cinfo.o obj/dir.o obj/display.o obj/echo.o obj/ex…
usage: mg [-hnRsS] [-b file] [-f mode] [-u file] [+number] [+number:col] [file ...]
step3 help exit: 0
step4 batch exit: 0
step5 install exit: 0
step5 installed batch exit: 0
Everything verifies from a clean state. The final answer:
tokens used
1,065,006
Everything verifies from a clean state. The final answer:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 15 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Unlicense, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

alpine-linuxbsdcygwindebiandocker-imagedragonflydragonflybsdeditoremacsfreebsdillumoslinuxmacosmicro-emacsmusl-libcnetbsdopenbsdsolaristext-editorunix

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/mg.svg)](https://argusic.com/subject/mg)

Questions

Does mg run?
Yes. mg runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test mg?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7bae32d01051. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test mg?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does mg take to install?
15 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does mg need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mg?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for mg?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion