Alacritty doesn't seem to be working with wal
See original GitHub issueI installed Void Linux today and finally managed to get pywal working (it only has py3.5 so I compiled 3.6.1 with pyenv) and since it doesn’t have Termite (my go-to terminal) in it’s repos I decided to try Alacritty (it’s supposed to be fast). So turns out it’s dash-fast, as in “lacks too many useful features” (probably because it’s still in alpha). The printf "%b" "\033]11;#ff0000\007"
does nothing so I guess you should add it to the list. I tried to make it work with wal by having a config.yml
that contains non-color options and an auto-generated colors.yml
that has colors (used termcolors to convert to Alacritty’s format), what I did was add this function:
function fix_alacritty() {
local dir="${HOME}/.config/alacritty"
rm "${dir}/alacritty.yml"
cat "${dir}/config.yml" "${dir}/colors.yml" >> "${dir}/alacritty.yml"
}
And call it in the script that gets executed after wal, turns out Alacritty needs everything to be in specific positions for the thing to work (it is possible with some mad regex-foo or yaml parsing, both of which I’m no good at and not going to try doing since the benefits aren’t that good, not being able to change colors on the fly is a bummer)
So I guess it’s not really an issue with wal but I’m just letting you know
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (10 by maintainers)
Top GitHub Comments
I just wrote a workaround that may help Mac users who want wal colors in Alacritty: https://github.com/egeesin/alacritty-color-export
It might be worth opening a bug on their tracker. Alacritty works fine on Linux.