Alacritty

  • 1
  • 2
  • 3

0.10.1 | Updated: 01 Mar 2022

Downloads:

42,407

Downloads of v 0.10.1:

1,548

Maintainer(s):

Software Author(s):

  • Joe Wilm

  • 1
  • 2
  • 3
Alacritty 0.10.1

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Exemption:

Package needs to be rebooted after VcRedist140 installed.

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Alacritty, run the following command from the command line or from PowerShell:

>

To upgrade Alacritty, run the following command from the command line or from PowerShell:

>

To uninstall Alacritty, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade alacritty -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade alacritty -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install alacritty
  win_chocolatey:
    name: alacritty
    version: '0.10.1'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'alacritty' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '0.10.1'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller alacritty
{
    Name     = "alacritty"
    Version  = "0.10.1"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'alacritty':
  ensure   => '0.10.1',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 01 Mar 2022.

Description

Alacritty - A fast, cross-platform, OpenGL terminal emulator

About

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.

Features

You can find an overview over the features available in Alacritty here.

Further information

Configuration

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:

  1. $XDG_CONFIG_HOME/alacritty/alacritty.yml
  2. $XDG_CONFIG_HOME/alacritty.yml
  3. $HOME/.config/alacritty/alacritty.yml
  4. $HOME/.alacritty.yml

Windows

On Windows, the config file should be located at:

%APPDATA%\alacritty\alacritty.yml

Contributing

A guideline about contributing to Alacritty can be found in the
CONTRIBUTING.md file.

FAQ

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][tmux]) nor
niceties like a GUI config editor.

IRC

Alacritty discussions can be found in #alacritty on freenode.


Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Alacritty 0.10.0 1085 Wednesday, January 26, 2022 Approved
Alacritty 0.9.0 3388 Sunday, August 8, 2021 Approved
Alacritty 0.8.0 2187 Wednesday, May 19, 2021 Approved
Alacritty 0.7.2 2253 Thursday, March 4, 2021 Approved
Alacritty 0.7.1 1728 Tuesday, January 12, 2021 Approved
Alacritty 0.7.0 209 Monday, January 11, 2021 Approved
Alacritty 0.6.0 1540 Wednesday, November 25, 2020 Approved
Alacritty 0.5.0 2857 Monday, August 3, 2020 Approved
Alacritty 0.4.3.20200606 3139 Saturday, June 6, 2020 Approved

Added

  • Option font.builtin_box_drawing to disable the built-in font for drawing box characters

Changed

  • Builtin font thickness is now based on cell width instead of underline thickness

Fixed

  • OSC 4 not handling ?

  • ? in OSC strings reporting default colors instead of modified ones

  • OSC 104 not clearing colors when second parameter is empty

  • Builtin font lines not contiguous when font.offset is used

  • font.glyph_offset is no longer applied on builtin font

  • Buili-in font arcs alignment

  • Repeated permission prompts on M1 macs

  • Colors being slightly off when using colors.transparent_background_colors

Discussion for the Alacritty Package

Ground Rules:

  • This discussion is only about Alacritty and the Alacritty package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Alacritty, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus