ov

🎑Feature-rich terminal-based text viewer. It is a so-called terminal pager.

Runssource: GitHubhomepageGoMITcommit e799baf99eb5

Go, MIT licensed. The project labels itself: cli, command line, command line tool, go, golang, incremental search, less and more.

ov runs. An Argusic agent installed it in 4 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The Go project 'ov' (a feature-rich terminal pager) builds with `go build`, all 4 test packages pass (ov, biomap, indexmap, oviewer), and the compiled binary accepts piped input and responds to --help and --version flags.

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.03 (measured)
recorded runs
2
last tested
stars
2,053
forks
53
open issues
29
watchers
5
size
14 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.

Install time
4 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
go test -count=1 ./... exited 0 (4 ok, 6 no test files); ./ov --version printed 'ov version test rev:test'; pipe input with -X flag echoed content correctly
Model tokens used
24,954
Exact commit tested
e799baf99eb5
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.

ok    github.com/noborus/ov  0.052s
ok    github.com/noborus/ov/biomap  0.004s
?     github.com/noborus/ov/examples/exec  [no test files]
?     github.com/noborus/ov/examples/header  [no test files]
?     github.com/noborus/ov/examples/search  [no test files]
?     github.com/noborus/ov/examples/simple  [no test files]
?     github.com/noborus/ov/examples/tail  [no test files]
ok    github.com/noborus/ov/indexmap  0.007s
ok    github.com/noborus/ov/oviewer  1.348s
?     github.com/noborus/ov/tools/gen-keybind  [no test files]
tokens used
24,954

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.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • 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

  • Took 4 minutes to install, slower than the median of the 126 comparable projects Argusic has measured.

Of the 127 cli projects Argusic has installed and timed, ov was the 83rd fastest to reach a running state, and 115 of 127 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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/3Runs100.000.03
Argusic Runner1/3Runs100.000.08

Topics (from GitHub)

clicommand-linecommand-line-toolgogolangincremental-searchlessmorepagertailtcellterminalterminal-pagertui

Embed the badge

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

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

Questions

Does ov run?
Yes. ov runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test ov?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e799baf99eb5. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ov?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ov take to install?
4 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 ov need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ov?
Nothing did, in the recorded run: zero errors between clone and running.
How does ov compare with the alternatives?
Of the 127 cli projects Argusic has installed and timed, ov was the 83rd fastest to reach a running state, and 115 of 127 reached one at all.
Where is the evidence for ov?
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