Re: Do not render correctly colors on ssh terminal

[Yuri Khan <yuri.v.khan@gmail.com>]

On Fri, 6 Oct 2023 at 02:08, Vincenzo Palazzo
<vincenzopalazzodev@gmail.com> wrote:

> I have a problem that I was never able to solve and I
> always try to switch on another editor when I am coding on my remote machine.
>
> However, I think that I solution should be somewhere for this kind of problem
> and that I am the only one that is finding this problem.
>
> MY doom [1] configuration with emacs 29.1 on my host machine is rendered
> in the terminal as [2] but the same configuration on the same file in a
> ssh session emacs is rendered as [3].

The thread devolved into getting you to use Tramp, but the answer to
your original problem is somewhere in terminal capability definitions.

On your local machine, you probably have TERM=xterm-256color or
similar in your environment and you have a terminfo database entry for
that terminal. Typing ‘infocmp’ probably says ‘colors#0x100’ or
‘colors#256’ somewhere near the top.

On your remote machine, you should still have TERM=xterm-256color, as
‘ssh’ forwards that variable by default. However, if the corresponding
terminfo database entry is not installed, applications will not detect
that your terminal is capable of displaying 256 colors. ‘infocmp’ will
say colors#8 or something similar.

How you install the required terminfo entries will depend on your
distribution. On Debian-based distros,
‘/usr/share/terminfo/x/xterm-256color’ is installed by the package
‘ncurses-base’.

There is also a possibility that your theme assumes 24-bit color, and
your remote machine is not advertising that capability. See
https://www.gnu.org/software/emacs/manual/html_node/efaq/Colors-on-a-TTY.html
for a summary where Emacs looks before it decides whether 24-bit color
is or is not available.