bug#54722: closed (28.1: colors in alacritty terminal)

[GNU bug Tracking System]

Your message dated Sat, 9 Apr 2022 17:23:28 +0200
with message-id <YlGk8EQ4m0F9jkHL@ot.lublin.se>
and subject line Re: bug#54722: Acknowledgement (28.1: colors in alacritty 
terminal)
has caused the debbugs.gnu.org bug report #54722,
regarding 28.1: colors in alacritty terminal
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
54722: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=54722
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: 28.1: colors in alacritty terminal Date: Tue, 5 Apr 2022 10:44:16 +0200

I'm trying out emacs 28, coming from 27.2 on an Arch system. I have an issue
with the colors displayed when running in alacritty terminal. Running in
urxvt and xterm is fine.

I see different hues of most colors, and list-colors-display looks
completely different in alacritty vs urxvt. I'm attaching a screenshot of
what it looks like. On the left is alacritty, on the right urxvt. Running
emacs -nw -q --no-site-file -nsl

In #emacs on libera I was pointed at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48439 and I tried removing the
alacritty alias, but that didn't help.

My system has ncurses 6.3 which does have terminfo for alacritty.

-- 
Daniel
lublin.se

1649146161.png
Description: PNG image

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#54722: Acknowledgement (28.1: colors in alacritty terminal)
>
>
>
>
> Date: 
>
> Sat, 9 Apr 2022 17:23:28 +0200
>
>
>
>
> I also filed this here: https://github.com/alacritty/alacritty/issues/5995
>
> Since, I played around a bit more. Also tried gnome-terminal (which I never
> really used), and emacs 28 in it looks identical to alacritty. I'm thinking
> that emacs 28 and alacritty might actually be doing things correctly now,
> and it was just broken before. urxvt and xterm might be flawed, or lack
> features.
>
> As kchibisov summed it up in the above report "Then it seems like it was
> broken before and you've liked it, but now it's correct and you don't? So
> you should update your emacs settings?". Yes, I think so.
>
>
> --- End Message ---