[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: truecolor option not functional
From: |
Amadeusz Sławiński |
Subject: |
Re: truecolor option not functional |
Date: |
Fri, 30 Mar 2018 08:32:28 +0200 |
On Thu, 29 Mar 2018 18:16:46 -0400
Jon Gjengset <address@hidden> wrote:
> I've been trying to enable truecolor support in my screen session after
> stumbling upon commit 9668a1ab00fea2096555a33cb962cc865b86e74a[1].
> However, `:truecolor on` gives `unknown command 'truecolor'`, and
>
> truecolor on
>
> in my ~/.screenrc doesn't seem to make any difference. Am I missing
> something obvious here? I've set my term to alacritty-256color (which I
> have a terminfo file for), and am testing with the command
>
> printf "\x1b[38;2;255;100;0mTRUECOLOR\x1b[0m\n"
>
> which should show `TRUECOLOR` in an orange font. This works fine
> directly in my terminal, but not through screen. My screenrc is
> otherwise empty (that is, beyond `truecolor on` and `term
> alacritty-256color`).
>
> Any advice would be useful!
> Cheers,
> Jon
>
> [1]:
> https://git.savannah.gnu.org/cgit/screen.git/commit/?id=9668a1ab00fea2096555a33cb962cc865b86e74a
>
> _______________________________________________
> screen-users mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/screen-users
Hey,
did you build screen from master branch?
Releases are done from screen-v4 and master is development branch for
next version (v5).
Cheers,
Amadeusz