ttt

TTT Editor (Terminal Text Tool): A real alternative to VS Code, Zed, and Sublime that runs in your terminal. A TUI that feels like GUI. Single binary, zero config.

Not yet testedsource: GitHubhomepageGoMITcommit 63f10d525283

Go, MIT licensed. The project labels itself: cli, code editor, developer tools, diff, editor, git integration, go and golang.

ttt has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict
Not yet tested
Argusic Score
not scored yet
recorded runs
0
last tested
-
stars
397
forks
30
open issues
66
watchers
3
size
56 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.

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

No recorded runs.

Topics (from GitHub)

clicode-editordeveloper-toolsdiffeditorgit-integrationgogolangherdr-pluginidelspsyntax-highlightingtcellterminalterminal-emulatortexttext-editorttttuivscode-alternative

Embed the badge

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

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

Questions

Does ttt run?
ttt has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test ttt?
On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for ttt?
All 0 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