| commit | cb4d2c0a3b20adc4c0603dcfb9447e9ebf72eae5 | [log] [tgz] |
|---|---|---|
| author | Christian Dürr <contact@christianduerr.com> | Fri Nov 16 11:13:38 2018 +0100 |
| committer | Christian Dürr <contact@christianduerr.com> | Fri Nov 16 11:13:38 2018 +0100 |
| tree | 0dc4d8c62882e70a583c01770607ce3c47944048 | |
| parent | e66f23ad97c8df42192d07650109d42de3c767c9 [diff] |
Add option for keeping log files Since it's not unusual to spawn a lot of different terminal emulators without restarting, Alacritty can create a ton of different log files. To combat this problem, logfiles are now removed by default after Alacritty has been closed. If the user wants to persist the log of a single session, the `--persistent_logging` option can be used. For persisting all log files, the `persistent_logging` option can be set in the configuration file
Alacritty is the fastest terminal emulator in existence. Using the GPU for rendering enables optimizations that simply aren't possible in other emulators. Alacritty currently supports macOS, Linux, and Windows.
Alacritty is focused on simplicity and performance. The performance goal means it should be faster than any other terminal emulator available. The simplicity goal means that it doesn't have features such as tabs or splits (which can be better provided by a window manager or terminal multiplexer) nor niceties like a GUI config editor.
The software is considered to be at an alpha level of readiness--there are 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.
Some operating systems already provide binaries for Alacritty, for everyone else the instructions to build Alacritty from source can be found here.
pacman -S alacritty
Using cargo deb, you can create and install a deb file.
git clone https://github.com/jwilm/alacritty.git cd alacritty cargo install cargo-deb cargo deb --install
zypper in alacritty
xbps-install alacritty
emerge x11-terms/alacritty
pkg install alacritty
Prebuilt binaries for Linux, macOS, and Windows can be downloaded from the GitHub releases page.
Although it‘s possible the default configuration would work on your system, you’ll probably end up wanting to customize it anyhow. There is a default alacritty.yml, alacritty_macos.yml, and alacritty_windows.yml at the Git repository root. Alacritty looks for the configuration file as the following paths:
$XDG_CONFIG_HOME/alacritty/alacritty.yml$XDG_CONFIG_HOME/alacritty.yml$HOME/.config/alacritty/alacritty.yml$HOME/.alacritty.ymlIf none of these paths are found then $XDG_CONFIG_HOME/alacritty/alacritty.yml is created once Alacritty is first run. On most systems this often defaults to $HOME/.config/alacritty/alacritty.yml.
Many configuration options will take effect immediately upon saving changes to the config file. The only exception is the font and dimensions sections which requires Alacritty to be restarted. For further explanation of the config file, please consult the comments in the default config file.
On Windows the config file is located at:
%UserProfile%\alacritty.yml
If you run into a problem with Alacritty, please file an issue. If you‘ve got a feature request, feel free to ask about it. Keep in mind that Alacritty is very much not looking to be a feature-rich terminal emulator with all sorts of bells and widgets. It’s primarily a cross-platform, blazing fast tmux renderer that Just Works.
Is it really the fastest terminal emulator?
In the terminals I‘ve benchmarked against, Alacritty is either faster, WAY faster, or at least neutral. There are no benchmarks in which I’ve found Alacritty to be slower.
macOS + tmux + vim is slow! I thought this was supposed to be fast!
This appears to be an issue outside of terminal emulators; either macOS has an IPC performance issue, or either tmux or vim (or both) have a bug. This same issue can be seen in iTerm2 and Terminal.app. I've found that if tmux is running on another machine which is connected to Alacritty via SSH, this issue disappears. Actual throughput and rendering performance are still better in Alacritty.
My arrow keys don't work.
It sounds like you deleted some key bindings from your config file. Please reference the default config file to restore them.
Alacritty discussion can be found in #alacritty on freenode.
Wayland support is available, but not everything works as expected. Many people have found a better experience using XWayland which can be achieved launching Alacritty with the WAYLAND_DISPLAY environment variable cleared:
env WAYLAND_DISPLAY= alacritty
If you're interested in seeing our Wayland support improve, please head over to the Wayland meta issue on the winit project to see how you may contribute.
Alacritty is released under the Apache License, Version 2.0.