Geany
Geany is a lightweight cross-platform IDE built around GTK and Scintilla, with syntax highlighting, completion, symbols, build commands, an embedded terminal and plugins.
What Geany is for
Geany is suited to developers who want a fast editor with projects, symbol navigation, completion and build output without a large integrated stack. It works well for teaching, scripts and small to medium cross-language projects, while compilers, interpreters, debuggers and language services remain separate components.
Version and platforms
Geany 2.1 was released on 2025-07-06. Windows provides signed installers, macOS provides Intel and Apple Silicon disk images, and Linux or BSD commonly use distribution packages or source archives. The release updates Scintilla and Lexilla, adds theme and native file-dialog improvements, and fixes silent truncation of files containing NUL bytes.
Toolchain, plugins and source boundaries
Recognizing a file type does not mean its compiler is installed. Build commands, external terminals and plugins can run local programs with the active user's permissions. Check commands and plugins before opening an unknown project, use a normal account and back up source, project settings, locked dependencies and version history separately.
Maintenance note
This page was reviewed on 2026-08-23 against Geany 2.1, platform packages, signed installer status, feature documentation and GPL-2.0-or-later licensing.
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 Geany to this cloud drive
Baidu Netdisk
Save Geany to this cloud drive
Geany 2.1 installation, project setup and build commands
Install Geany and the required language toolchain, then use a small project to verify encoding, completion, build commands and output navigation before enabling trusted plugins.
Before you start
- Identify the compiler or interpreter required by the target language and verify its version and PATH in a system terminal.
- Back up existing settings, project files and custom file-type definitions; a project session does not replace version control.
- Prefer the signed Windows installer, the matching Intel or Apple Silicon macOS image, or a distribution package on Linux.
Installation steps
- 01
Install the editor and toolchain
Complete the Geany installation, then run the target compiler or interpreter outside the IDE. Fix PATH before changing IDE build settings.
- 02
Open a sample project and check encoding
Open a small directory and verify syntax highlighting, line endings, character encoding and symbols, including files with Chinese text or NUL-byte edge cases.
- 03
Configure build and run commands
Set compile, build and execute commands for the file type or project, using a harmless sample to check the working directory, exit code and message navigation.
Quick start
- 01
Create a project instead of a single-file session
Set a base directory and file patterns for a small codebase, confirm relative paths between project settings and sources, and back them up together.
- 02
Use completion and symbol navigation
Use symbols, call tips, folding and multi-cursor editing for routine work. Treat completion as assistance rather than a substitute for compilation and tests.
- 03
Fix the first real build error
Run a build and jump from the message window to the reported file and line. Reproduce a failed command in the system terminal to separate path and permission issues.
Usage tips
- Build commands, external terminals and plugins execute with the current user's permissions; inspect preset commands before opening an unknown project.
- Plugins can take over completion, navigation and highlighting. Reproduce conflicts with plugins disabled and a clean configuration.
- Project sessions record open files and settings, not Git history, dependency versions or build artifacts; reproducible projects need those records separately.
Troubleshooting and uninstall
Why does a build report that a command is missing?
Run the same command in a system terminal, verify the toolchain, then check Geany's inherited PATH, project working directory and build template. GUI-launched macOS apps may receive a different environment.
Why are completion, terminal or plugins failing?
Disable the related plugin and retest with defaults, confirm compatibility with Geany 2.1 and the current architecture, and remember that embedded terminals depend on platform components.
- Export project and custom settingsSave source, project files, custom commands, file types and plugin lists, and verify changes are committed or backed up.
- Remove the editor and optional configurationUninstall the application or package and keep user settings only when they are needed for a reinstall. Remove compilers, interpreters or Git separately after checking shared dependencies.
Frequently asked questions
Is Geany a complete compiler suite?
No. It provides editing, projects, build commands and output navigation, while compilers, interpreters, debuggers and most language tools must be installed and configured separately.
Why prefer the signed Windows installer?
The signature helps confirm the publisher and post-signing integrity, but it does not replace source review, hash checking or security scanning. Use the signed build when there is no specific test need for an unsigned package.
Does a Geany project file include all source code?
No. It mainly stores paths, sessions and build settings. Source files remain independent, so keep version control and a separate backup instead of copying only the project file.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.