all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Do not render correctly colors on ssh terminal
Date: Fri, 6 Oct 2023 23:07:17 +0200	[thread overview]
Message-ID: <CAKy8djRNfeyby5uWRS6-Arhtdn6dDaN4YKHJNPLkTHRatdocpA@mail.gmail.com> (raw)
In-Reply-To: <874jj4en2u.fsf@dataswamp.org>

Hi,

>You can configure the colors for xterm manually in
~/.Xresources, then do 'xrdb ~/.Xresources' in ~/.xinitrc.

In what terminal? the ssh one or the local one?

Cheers,

Vincent.

On Fri, Oct 6, 2023 at 2:51 PM Emanuel Berg <incal@dataswamp.org> wrote:
>
> Vincenzo Palazzo wrote:
>
> > I think the two configurations should be shown the same.
> > I also try to use `export TERM='xterm-256color'` or `export
> > TERM='xterm'` but this does not work for me.
>
> You can configure the colors for xterm manually in
> ~/.Xresources, then do 'xrdb ~/.Xresources' in ~/.xinitrc.
>
> ! this file:
> !   https://dataswamp.org/~incal/conf/.Xresources
>
> ! xterm
> xterm*background:      #000000
> xterm*cursorBlink:     false
> xterm*cursorcolor:     #000000
> xterm*faceName:        DejaVu Sans Mono Bold:pixelsize=12
> xterm*foreground:      #dddddd
> xterm*metaSendsEscape: true
>
> ! colors (blue red green yellow blue magenta cyan white)
> ! normal
> xterm*color0: #000000
> xterm*color1: #ff3232
> xterm*color2: #009600
> xterm*color3: #bebe00
> xterm*color4: #6464ff
> xterm*color5: #af6400
> xterm*color6: #00b4b4
> xterm*color7: #969696
>
> ! bright/bold
> xterm*color8:  #5a5a5a
> xterm*color9:  #ff4b4b
> xterm*color10: #00b400
> xterm*color11: #ff7f00
> xterm*color12: #7d7dff
> xterm*color13: #eb4beb
> xterm*color14: #5affff
> xterm*color15: #d2b48c
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>



  reply	other threads:[~2023-10-06 21:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 19:07 Do not render correctly colors on ssh terminal Vincenzo Palazzo
2023-10-05 22:11 ` Emanuel Berg
2023-10-06 21:07   ` Vincenzo Palazzo [this message]
2023-10-07 11:29 ` Michael Albinus
     [not found]   ` <CAKy8djQF5zQts75xdNpGaWY5rzpMjkzaqqLf+HAM6OUFr9K_EQ@mail.gmail.com>
     [not found]     ` <8734ymochn.fsf@gmx.de>
     [not found]       ` <CAKy8djRH93g=ydi=PvZ5FmHQp=CJkviDENE0YY+Fqx3B99L=nw@mail.gmail.com>
     [not found]         ` <87jzryijen.fsf@gmx.de>
2023-10-07 14:49           ` Vincenzo Palazzo
2023-10-07 15:42             ` Michael Albinus
2023-10-07 16:38               ` Vincenzo Palazzo
2023-10-07 16:46                 ` Michael Albinus
2023-10-07 17:10                   ` Vincenzo Palazzo
2023-10-07 17:13                     ` Michael Albinus
     [not found]                       ` <CAKy8djQaA=Qcgr7vTt9H3SnPCi2vGkMmzaRPgse0CjsQP_mhVA@mail.gmail.com>
2023-10-08  7:29                         ` Michael Albinus
2023-10-08 18:15                           ` Vincenzo Palazzo
2023-10-08 19:24                             ` Michael Albinus
2023-10-09  7:53                               ` Vincenzo Palazzo
2023-10-09  7:58                               ` Vincenzo Palazzo
2023-10-09  8:18                                 ` Michael Albinus
     [not found]                                   ` <CAKy8djS35rVJQSC8vNFaderSP-mSuxqT7ScC9d9sbkK3QRVAzg@mail.gmail.com>
2023-10-09  9:24                                     ` Michael Albinus
2023-10-09 14:30                                       ` Vincenzo Palazzo
2023-10-09 14:42                                         ` Emanuel Berg
2023-10-10  9:13                                           ` Vincenzo Palazzo
2023-10-09 16:12                                         ` Michael Albinus
2023-10-09 16:16                                           ` Yuri Khan
2023-10-09 16:22                                             ` Michael Albinus
2023-10-09 16:39 ` Yuri Khan
2023-10-10 17:23   ` Vincenzo Palazzo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKy8djRNfeyby5uWRS6-Arhtdn6dDaN4YKHJNPLkTHRatdocpA@mail.gmail.com \
    --to=vincenzopalazzodev@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.