micro
micro 2.0.15 is an approachable terminal text editor with familiar shortcuts, mouse input, multiple cursors, splits, syntax highlighting, persistent undo and Lua plugins.
What micro does
micro brings common desktop-editor behaviors to a terminal, including keyboard shortcuts, mouse support, multiple cursors, splits, search and replace, syntax highlighting and persistent undo. Lua plugins can extend the editor but add code and permission considerations.
Version and package boundaries
Version 2.0.15 for Windows is distributed as a self-contained 64-bit archive. Basic editing does not need an external runtime, while plugins, clipboard integration and external commands can depend on the terminal or other tools.
Terminal compatibility
A modern terminal with 256 colors or true color, mouse and Unicode support provides the most predictable experience. Cygwin and MinGW are not treated as the same supported target as the native Windows build.
Configuration and plugin scope
Persistent undo, settings and plugins write to the user profile. Back up configuration, install one trusted plugin at a time and avoid testing unknown Lua code in an elevated terminal.
Maintenance note
Review date: 2026-08-23. The page was checked against micro 2.0.15, the Windows x64 archive, terminal capabilities, plugin boundaries and persistent configuration.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave micro to this cloud drive
Baidu Netdisk
Save micro to this cloud drive
micro 2.0.15 Windows terminal editing guide
Start with a disposable file, verify saving, undo, clipboard and terminal colors, then practice splits and multi-cursor editing before installing a trusted plugin.
Before you start
- Use a modern Windows terminal with 256-color or true-color, mouse and Unicode support.
- Prepare a disposable text file and put important source or configuration under version control or backup.
- Keep the default plugin set for the first baseline so extension behavior does not obscure editor issues.
Installation steps
- 01
Extract the Windows archive
Unpack the 64-bit ZIP into a fixed tools directory, run micro -version and verify the executable before adding the directory to PATH.
- 02
Test a full-path launch
Open a sample file by full path, check colors, mouse, Unicode, copy and paste and common control keys, then close and reopen the file.
- 03
Configure a stable command path
Add the tools directory to the user PATH only after the test works, and check that another micro executable is not shadowing the intended version.
Quick start
- 01
Open and save a file
Move with keys or mouse, edit a small sample, save with the expected command and reopen it to verify content and encoding.
- 02
Use built-in help
Press Ctrl+E to open the command bar, enter help and record the current shortcuts before changing any bindings.
- 03
Enable extensions gradually
Practice splits, multiple cursors, search and persistent undo first, then install one reviewed plugin at a time with a clear disable path.
Usage tips
- Alt keys, mouse and clipboard events can differ between terminals. Validate important edits on a small file before using a remote session or automation.
- Plugin management depends on version metadata and network access, while unversioned script builds can complicate plugin discovery.
- Persistent undo and configuration can retain paths and editing history in the user profile, which matters on shared devices.
Troubleshooting and uninstall
Why is syntax highlighting missing or hard to read?
Use a terminal with 256-color or true-color support and a suitable theme, then switch to the simple palette to separate terminal capability from configuration.
Why is a shortcut intercepted by the terminal or operating system?
Check terminal, input-method and system shortcut settings, then remap the key in micro. Change one layer at a time so the conflict remains diagnosable.
- Remove the executable from PATHDelete the tools directory from the user PATH, close terminals that use micro and remove the executable after confirming no task still calls it.
- Clean user state selectivelyBack up needed settings, plugins and persistent undo data before removing the micro configuration directory.
Frequently asked questions
Does the Windows micro archive need another runtime?
The prebuilt native program is self-contained for basic editing. Plugins, clipboard integration and external commands may still depend on the terminal or another installed tool.
Is Cygwin or MinGW the same supported environment as native Windows?
The project supports the native Windows build, while Cygwin and MinGW have separate compatibility considerations and should be tested as distinct environments.
Can I install any micro plugin immediately?
Review its source, maintenance state and code first, back up configuration and install one plugin at a time without using an elevated terminal.