From Fedora Project Wiki

Revision as of 16:41, 25 June 2012 by Mitr (talk | contribs)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This feature page needs to explain better how the feature will affect remote logins.

What does "degraded experience" mean? Will I simply get the same colors on the remote system that I get now, or will I lose a lot of other features?

If I SSH to a system that doesn't support 256 colors, sometimes from an X terminal, sometimes from a Linux virtual console, and maybe sometimes from Screen or some other kind of terminal, how can I set things up once and for all so that it works right in all cases? Is it enough to set TERM=xterm in all cases?

What if I SSH to a Fedora box from a system that supports only eight colors, or even just black and white?

Does the feature affect serial consoles, Telnet, Kermit et cetera in any way?

Rombobeorn 15:09, 25 June 2012 (UTC)

  • SSH is the major downside of this. There should be a way to "unbreak" systems automatically (ideally by editing ~/.ssh/config, or, in the worst case setting up a shell alias), and it should be documented in the release notes.
  • Why is it better to add a script to /etc/profiles.d than to patch specific terminal emulators to set TERM to a 256-color version? This would allow e.g. gnome-terminal run with 256 colors, but a different terminal emulator that doesn't support 256 colors to continue setting TERM=xterm .

--Mitr 16:41, 25 June 2012 (UTC)