TTT's recommended Linux install pipes a script from GitHub straight into your shell. Yet It's FOSS says the editor "often doesn't feel like a terminal editor at all." If you come from VS Code, Zed or Sublime and don't want to learn Vim, the real question is how much editor you want inside the terminal.
According to It's FOSS, TTT skips emulating traditional terminal editors and aims for a GUI-like experience with virtually no configuration. This guide is a decision aid, not another TTT review. It compares TTT with nano, micro, Microsoft Edit and Helix (the modal contrast) on the factors that decide the choice.
A note on sourcing: TTT's features below come from the It's FOSS article. Everything about the other editors comes from general knowledge and is marked verify in docs, so check each project's official documentation before you commit. This guide is based on reading, not hands-on testing of any editor.
Setup effort and install method
TTT's recommended Linux install is an installer script piped into a shell. It's FOSS describes it as "No package, just an installer script curled right into your system." The command is:
curl -sSfL https://raw.githubusercontent.com/eugenioenko/ttt/main/install.sh | sh
It's FOSS says the script places the binary in ~/.local/bin, and that prebuilt binaries exist for portable use. It does not mention distro packages, so check the project's repository for any.
The other editors differ mainly in how likely they are to be present already. Nano ships by default on many distributions (verify in docs for your distro). Micro and Helix are commonly available through distro repositories or as single downloads (verify in docs). It's FOSS calls Microsoft's open source Edit worth a look, but you need to check its Linux packaging status in its official repository.
On a locked-down server, install friction matters more than features. An editor you can already run beats one you must fetch.
Mouse support and familiar shortcuts
This is where TTT makes its strongest case. It's FOSS says you can click to place the cursor, drag to select, and right-click for context menus that change depending on where you click.
Multi-cursor editing works with Ctrl+D (select the next occurrence) and Alt+Click, which It's FOSS says will feel familiar to Sublime users. Workspace search uses Ctrl+K F, and search and replace uses Ctrl+K R.
The others take different approaches (all verify in docs):
- nano shows its shortcuts at the bottom of the screen, which makes it easy to learn. Mouse support is usually something you enable (verify).
- micro is generally reported to use familiar Ctrl+S, Ctrl+C and Ctrl+V shortcuts, with mouse support (verify).
- Microsoft Edit is reported to have a menu bar and mouse interaction, in the spirit of classic DOS-era editors (verify).
- Helix is modal. It is not Vim, but you still have to learn a keymap. It's FOSS mentions Helix only as the origin of the author's multi-cursor habit.
One caveat applies to every editor over SSH: mouse events, true color and right-click behavior depend on your local terminal emulator, not just the editor. It's FOSS does not discuss remote use, so test any candidate in your own SSH setup before you rely on it. We cover related ground in how to check laptop linux kernel support before 7.4 explained.
LSP, Git and an integrated terminal
Do you need these? If you edit scripts and config files, probably not. If you work in multi-file projects, they remove a lot of context switching.
It's FOSS credits TTT with all three:
- LSP: completion works once you install the language server for your language, and the project maintains a setup guide.
- Git: a Changes panel handles stage, unstage, discard, commit, pull, push and sync. It comes with a diff viewer, gutter indicators and inline blame.
- Terminal: the integrated terminal is described as a full emulator with tabs, true color and scrollback.
Search is built on ripgrep. It's FOSS does not say whether you must install ripgrep separately, so confirm that in the TTT docs.
TTT also supports Lua plugins that run in a sandbox and must request permissions, with an in-editor install panel. Multi-folder workspaces save to a .ttt file.
For the other editors (verify in docs for each):
- Helix is generally described as having built-in LSP, but no Git panel or terminal pane.
- Micro has a plugin system, but LSP and Git depth depend on plugins.
- Nano is minimal by design.
- Edit's feature scope should be read from its repository.
This comparison is inference, not a tested conclusion. If you want LSP and a Git panel with no plugin hunting, TTT is the editor It's FOSS credits with all of them built in. The others need checking in their docs. For more on this, see fix ea app games on linux: switch proton versions in steam: the details.
When a GUI-like TUI is the wrong choice
It's FOSS notes that plenty of terminal users prefer apps that don't mimic desktop software. If that describes you, TTT's direction may annoy you.
Three situations favor a lighter editor:
- Minimal or short-lived servers, where you can't or don't want to add binaries.
- Quick edits with
sudo, where startup simplicity and ubiquity matter more than panels. - Slow or flaky SSH links, where a heavy UI may feel worse. This is an inference, and It's FOSS gives no latency data.
Also weigh maturity. It's FOSS found TTT's approach refreshing, but you are installing it through a curl-to-sh script. For editing system files as root, a long-established editor is the conservative pick.
Comparison table
| Editor | Learning curve | Mouse | LSP | Git | Plugins | Install | |---|---|---|---|---|---|---| | TTT | Low, GUI-like shortcuts (It's FOSS) | Click, drag, context menus (It's FOSS) | Yes, install language servers (It's FOSS) | Changes panel, diff, blame (It's FOSS) | Lua, sandboxed (It's FOSS) | curl-to-sh script or prebuilt binary (It's FOSS) | | nano | Low (verify in docs) | Verify in docs | Verify in docs | Verify in docs | Verify in docs | Often preinstalled (verify in docs) | | micro | Low (verify in docs) | Verify in docs | Verify in docs | Verify in docs | Verify in docs | Repos or binary (verify in docs) | | Microsoft Edit | Low (verify in docs) | Verify in docs | Verify in docs | Verify in docs | Verify in docs | Check official repo | | Helix | Higher, modal (verify in docs) | Verify in docs | Verify in docs | Verify in docs | Verify in docs | Repos or binary (verify in docs) |
Also read: context: run local ai on ubuntu 26.10: ollama setup for beginners
Decision checklist
- You need an editor on every server with zero installs: pick nano, after confirming it is present (verify in docs).
- You want familiar shortcuts in a small, lightweight tool: try micro (verify in docs).
- You want a menu-driven feel and don't mind a Microsoft-authored tool: try Edit (verify in docs).
- You want LSP, a Git panel, an integrated terminal and workspaces in one binary: try TTT.
- You will learn a keymap in exchange for built-in LSP and multi-cursor: consider Helix (verify in docs).
Safe-install checklist for TTT
Piping a remote script to your shell runs whatever the server returns at that moment. These steps reduce the risk. They draw on the install details in the It's FOSS article and standard shell practice, and none of them was executed for this guide.
-
Download the script instead of piping it:
curl -sSfL -o install.sh https://raw.githubusercontent.com/eugenioenko/ttt/main/install.sh -
Read it with
less install.sh. Look at what it downloads, from where, and where it writes files. -
Run it only if you are satisfied:
sh install.sh. -
Or skip the script. Download a prebuilt binary from the project's releases and run it from a folder you choose, in portable mode. Check the release page for checksums and verify them if provided.
-
Verify with
ttt. If the command is not found, make sure~/.local/binis in your PATH (inference). -
To uninstall, remove
~/.local/bin/ttt. Check the TTT docs for any config or plugin directories it may have created.
Try it first as a normal user on a non-critical machine, not as root on a production server.
Who should choose what
If you edit over SSH on machines you don't control, learn nano's basics and carry on. If you want a lean, friendly upgrade, micro or Edit deserve a look once you verify their docs.
If your day looks like VS Code or Zed, with project search, Git and language servers, TTT is worth a safe trial. Use a downloaded and inspected script, or the portable binary. Pick Helix only if you accept a modal keymap in exchange for built-in language features.
