goneovim

A GUI frontend for neovim.

Runs with mockssource: GitHubGoMITcommit d6d80cc8d178

Go, MIT licensed. The project labels itself: cross platform, editor, go, golang, gui, ide, neovim and neovim guis.

goneovim runs, with stand-ins for the services it depends on. An Argusic agent installed it in 30 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go 1.22.2 installed at /home/runner/go; 45 Qt5 dev packages extracted at /home/runner/qt5; Go dependencies resolved; Qt5 pkg-config set up; editor tests compile/link but cannot execute without real Qt5 runtime

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.45 (measured)
recorded runs
2
last tested
stars
2,628
forks
69
open issues
103
watchers
26
size
33 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 goneovim, 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.

  • Qt5 system packages not installed (no root access)10 minutes
  • Qt5 CGo compilation fails cascade of missing headers10 minutes
  • Qt5 runtime libraries missing for linker3 minutes
  • Go 1.22.2 not installed1 minute
  • Test segfaults on stub Qt objects at runtime
Install time
30 minutes
Cold machine to finish
71 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
make test in /work/repo: go test ./editor compiled and linked editor.go and all test files; test binary ran, all tests failed with SIGSEGV on stub Qt objects
Model tokens used
709,428
Exact commit tested
d6d80cc8d178
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

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

**What was done:**
- Downloaded and installed Go 1.22.2 (the required version) from tarball
- Resolved all 14 Go dependencies listed in `go.mod`
- Extracted ~45 Qt5 `.deb` packages from Ubuntu's repos (no root access) into `/home/runner/qt5`
- Set up `Qt5Core`, `Qt5Gui`, `Qt5Widgets`, `Qt5Qml`, `Qt5Script`, and ~40 other Qt5 pkg-config fil…
- Generated Qt5 Go bindings in **stub mode** (`QT_STUB=true`) because full CGo compilation requires…
- `make test` (go test ./editor) compiles and links all 1300+ lines of test code
- The test binary segfaults at runtime because stub Qt objects (`gui.NewQKeyEvent`) return nil — re…
**Key blockers:**
1. No root access to install Qt5 system packages (the CI uses `sudo apt-get install libqt*5-dev qt*…
2. Neovim not available in the container
3. Full `make app` build additionally requires the qtdeploy toolchain which needs a working full Qt…

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

  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 30 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.

Of the 13 cross-platform projects Argusic has installed and timed, goneovim was the 10th fastest to reach a running state, and 10 of 13 reached one at all.

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 Runner2/3Runs with mocks92.000.45
Argusic Runner1/3Ran out of time0.000.09

Topics (from GitHub)

cross-platformeditorgogolangguiideneovimneovim-guisnvimnvim-pluginqttext-editor

Embed the badge

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

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

Questions

Does goneovim run?
goneovim runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 30 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test goneovim?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit d6d80cc8d178. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test goneovim?
The run that produced this verdict cost $0.45: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does goneovim take to install?
30 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 goneovim need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing goneovim?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does goneovim compare with the alternatives?
Of the 13 cross-platform projects Argusic has installed and timed, goneovim was the 10th fastest to reach a running state, and 10 of 13 reached one at all.
Where is the evidence for goneovim?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion