|Christian Duerr 28abb1f9c7 Fix out of order terminal query responses||3 days ago|
|.builds||1 month ago|
|.github||1 month ago|
|alacritty||3 days ago|
|alacritty_config_derive||3 weeks ago|
|alacritty_terminal||3 days ago|
|docs||1 week ago|
|extra||1 month ago|
|scripts||1 year ago|
|.agignore||4 years ago|
|.editorconfig||4 months ago|
|.gitattributes||1 year ago|
|.gitignore||5 months ago|
|CHANGELOG.md||6 days ago|
|CONTRIBUTING.md||3 months ago|
|Cargo.lock||4 days ago|
|Cargo.toml||4 months ago|
|INSTALL.md||3 months ago|
|LICENSE-APACHE||10 months ago|
|Makefile||5 months ago|
|README.md||1 month ago|
|alacritty.yml||5 days ago|
|rustfmt.toml||1 year ago|
Alacritty is a modern terminal emulator that comes with sensible defaults, but allows for extensive configuration. By integrating with other applications, rather than reimplementing their functionality, it manages to provide a flexible set of features with high performance. The supported platforms currently consist of BSD, Linux, macOS and Windows.
The software is considered to be at a beta level of readiness; there are a few missing features and bugs to be fixed, but it is already used by many as a daily driver.
Precompiled binaries are available from the GitHub releases page.
You can find an overview over the features available in Alacritty here.
Alacritty can be installed by using various package managers on Linux, BSD, macOS and Windows.
Prebuilt binaries for macOS and Windows can also be downloaded from the GitHub releases page.
For everyone else, the detailed instructions to install Alacritty can be found here.
You can find the default configuration file with documentation for all available fields on the GitHub releases page for each release.
Alacritty doesn't create the config file for you, but it looks for one in the following locations:
On Windows, the config file should be located at:
A guideline about contributing to Alacritty can be found in the
Is it really the fastest terminal emulator?
Benchmarking terminal emulators is complicated. Alacritty uses vtebench to quantify terminal emulator throughput and manages to consistently score better than the competition using it. If you have found an example where this is not the case, please report a bug.
Other aspects like latency or framerate and frame consistency are more difficult to quantify. Some terminal emulators also intentionally slow down to save resources, which might be preferred by some users.
If you have doubts about Alacritty's performance or usability, the best way to quantify terminal emulators is always to test them with your specific usecases.
Why isn't feature X implemented?
Alacritty has many great features, but not every feature from every other terminal. This could be for a number of reasons, but sometimes it's just not a good fit for Alacritty. This means you won't find things like tabs or splits (which are best left to a window manager or terminal multiplexer) nor niceties like a GUI config editor.
Alacritty discussions can be found in
#alacritty on freenode.
Alacritty is released under the Apache License, Version 2.0.