Here's what is written in the configuration file:
# Any items in the `env` entry below will be added as # environment variables. Some entries may override variables # set by alacritty itself. env: # TERM variable # # This value is used to set the `$TERM` environment variable for # each instance of Alacritty. If it is not present, alacritty will # check the local terminfo database and use `alacritty` if it is # available, otherwise `xterm-256color` is used. #TERM: alacritty
Now, the situation (by default) can occur that you from an alacritty terminal ssh to a remote server which does not a terminfo entry for alacritty. In such a case, no terminal features work because the server does not recognize the value of term. This can be fixed by explicitly setting the value.
For example, I have
export TERM=xterm-256color in my
.bashrc on my raspberry pi to fix this problem.
Lahwaacz questioned that setting the value of
TERM is a solution to the problem that the remote server does not have a terminfo entry for alacritty. So I pointed out how even the developers of alacritty use that value. Thus, alacritty is compatible with both
xterm-256color and it is possible to set it to fix that specific problem.
The minor differences between the two terminfo entries can be queried by running
$ infocmp alacritty xterm-256color