Couldn't we enable 256 colors by default on TERM?

Kévin Raymond shaiton at fedoraproject.org
Tue Jul 3 21:49:50 UTC 2012


Le mardi 26 juin 2012 à 22:31:09 (+0100), Pádraig Brady a écrit : 
> On 06/26/2012 07:35 PM, Chris Adams wrote:
> > Once upon a time, Miloslav Trmač <mitr at volny.cz> said:
> >> Another one is that connecting to systems that don't support xterm-256
> >> is not quite easy.  In particular, there appears to be no way to
> >> configure ~/.ssh/config so that "ssh oldhost" (and "ssh oldhost
> >> arbitrarycommand") transparently changes the TERM value - one would
> >> have to set up shell functions or something similar.  An extension of
> >> the ssh would be very nice - and failing that, an explicit recipe how
> >> to override TERM correctly would be welcome as well.
> > 
> > The OpenSSH devs might be open to such.  I'd be willing to take it up
> > with them and write a patch (if they'll accept it).

Yeah that should be the best thing: not sending $TERM through ssh (even telnet
would need it I think). Needs investigation.


This would avoid many hacks (profile.d, command in authorized_keys…)

[snip]

> The usual way to set/adjust TERM appropriate for the remote system
> is just to use the startup files there. This is what I add to ~/.profile
> on a solaris system for example:
> 
> [ "$SSH_CONNECTION" ] && export TERM=xterm
> 
> I'm not sure adding such functionality to .ssh/config
> would be of much benefit TBH.

As Chris said, 
the remote needs to be able to run this.


-- 
Kévin Raymond
(Shaiton)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20120703/0a096061/attachment.sig>


More information about the devel mailing list