Alacritty massive font

General system Applications
1

After installing Alacritty, I get massive font sizes on launch.

If I launch with WINIT_X11_SCALE_FACTOR=1 alacritty it looks fine, and I was told to ‘export this in the config file’.

Trouble is, I don’t know how - export WINIT_X11_SCALE_FACTOR=1 doesn’t work in the config file.

2

This should go in your ~/.bash_profile or ~/zshrc depending on the shell you use.

One thing I should tell is that I don’t use bash. There are multiple files where bash related configs can go and I cannot understand the difference. If ~/.bash_profile doesn’t work then you may want to try adding that export line in ~/.bashrc.
About zsh, I’m sure with ~/.zshrc since I use zsh myself.

2 Likes
3

Lol yes, I got it - actually in /etc/environment

# This file is parsed by pam_env module
#
# Syntax: simple "KEY=VAL" pairs on separate lines
#
WINIT_X11_SCALE_FACTOR=1

In my .zshrc I had to add ‘blur’ which also didn’t work out of the crate…

# BLUR ALACRITTY
if [[ $(ps --no-header -p $PPID -o comm) =~ '^alacritty$' ]]; then
        for wid in $(xdotool search --pid $PPID); do
            xprop -f _KDE_NET_WM_BLUR_BEHIND_REGION 32c -set _KDE_NET_WM_BLUR_BEHIND_REGION 0 -id $wid; done
fi

In alacritty.yml I set background_opacity: 0.7 so the blur gives a ‘hint’ of the background as I had (easily) set in Konsole.
However, uncommenting (and, of course, removing spaces) from blinking: On or blinking: Always just gets ignored.

Not sure it’s worth the bother…

But it’s still not right - the cursor won’t blink.

1 Like