alacritty doesn't find and set correct TERM

Created on 14 Dec 2018  路  3Comments  路  Source: alacritty/alacritty

Which operating system does the issue occur on?

Mageia Cauldron (mga7-dev0) x86_64

If on linux, are you using X11 or Wayland?

X11

On my system, alacritty doesn't set the correct TERM.

env | grep TERM
COLORTERM=truecolor
TERM=alacritty

This means that I don't get colors in neovim. When I set TERM manually to xterm-256colors, it works as expected. My wordaround is the export TERM in .zshrc.

Example
Alacritty vs Terminology - Neovim

alacritty -V
alacritty 0.2.4

Checked out from git master today.

S - config

Most helpful comment

alacritty is the correct TERM and Alacritty intentionally sets that if it is installed on the system. If it's set explicitly in the alacritty.yml, it will be used even when the terminfo file is not found though.

I'd probably recommend installing the alacritty terminfo over using xterm-256color, but if you're working on remote systems a lot, making use of xterm-256color can be a reasonable solution.

All 3 comments

This is defined in alacritty.yml

Ah, ok.

It is, by default, disabled and I didn't see that env was commented out. I'd just uncommented the TERM value and not env.

Thanks.

alacritty is the correct TERM and Alacritty intentionally sets that if it is installed on the system. If it's set explicitly in the alacritty.yml, it will be used even when the terminfo file is not found though.

I'd probably recommend installing the alacritty terminfo over using xterm-256color, but if you're working on remote systems a lot, making use of xterm-256color can be a reasonable solution.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

asilvadesigns picture asilvadesigns  路  3Comments

davidhewitt picture davidhewitt  路  3Comments

JMurph2015 picture JMurph2015  路  3Comments

dllud picture dllud  路  3Comments

chrisduerr picture chrisduerr  路  3Comments