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č m...@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
On 26/06/12 18:45, Miloslav Trmač wrote:
On Tue, Jun 26, 2012 at 3:24 AM, Matthew Garrett mj...@srcf.ucam.org wrote:
We discussed this in fesco today and had a couple of concerns.
Another one is that connecting to systems that don't support xterm-256
is not quite easy. In particular, there
On 06/26/2012 03:56 AM, Chris Adams wrote:
Once upon a time, Matthew Garrett mj...@srcf.ucam.org said:
On Mon, Jun 25, 2012 at 08:47:16PM -0500, Chris Adams wrote:
Trying to do this in profile scripts assumes that you only run local
terminals that come from Fedora and that have been tested.
2012/6/26 Chris Adams cmad...@hiwaay.net:
The newer terminal
programs have configuration menus for various things; do any of them set
it there? If they don't, I would think it would be relatively easy to
add (and hopefully upstreams would accept such patches).
Tried with XFCE's Terminal,
On 06/26/2012 02:37 PM, Thomas Moschny wrote:
2012/6/26 Chris Adams cmad...@hiwaay.net:
The newer terminal
programs have configuration menus for various things; do any of them set
it there? If they don't, I would think it would be relatively easy to
add (and hopefully upstreams would accept
On 06/26/2012 08:50 AM, Chris Adams wrote:
Once upon a time, Pádraig Brady p...@draigbrady.com said:
The main caveat with per terminal settings is that
it might be desired to provide config options per terminal.
Though I suppose users can always override TERM in their
startup files in the
On 06/26/2012 06:54 AM, Pádraig Brady wrote:
.
The main caveat with per terminal settings is that
it might be desired to provide config options per terminal.
Though I suppose users can always override TERM in their
startup files in the unlikely case they need to change
back to 'xterm' for
On Tue, Jun 26, 2012 at 10:20:56AM -0400, John Ellson wrote:
On 06/26/2012 06:54 AM, Pádraig Brady wrote:
.
The main caveat with per terminal settings is that
it might be desired to provide config options per terminal.
Though I suppose users can always override TERM in their
startup files
On Tue, 2012-06-26 at 10:20 -0400, John Ellson wrote:
On 06/26/2012 06:54 AM, Pádraig Brady wrote:
The main caveat with per terminal settings is that
it might be desired to provide config options per terminal.
Though I suppose users can always override TERM in their
startup files in the
On Tue, Jun 26, 2012 at 3:24 AM, Matthew Garrett mj...@srcf.ucam.org wrote:
We discussed this in fesco today and had a couple of concerns.
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
Miloslav Trmač wrote:
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
Once upon a time, Miloslav Trmač m...@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
On 06/26/2012 07:35 PM, Chris Adams wrote:
Once upon a time, Miloslav Trmač m...@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
Once upon a time, Pádraig Brady p...@draigbrady.com said:
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:
Well, that works when the other end is a system that has a
We discussed this in fesco today and had a couple of concerns. The
primary one was that handling this in profile seemed a bit fragile. It
seems like it would be more correct to have the terminals explicitly
set xterm-256 themselves if they're capable of it, rather than assuming
things about
Once upon a time, Matthew Garrett mj...@srcf.ucam.org said:
We discussed this in fesco today and had a couple of concerns. The
primary one was that handling this in profile seemed a bit fragile. It
seems like it would be more correct to have the terminals explicitly
set xterm-256 themselves
On Mon, Jun 25, 2012 at 08:47:16PM -0500, Chris Adams wrote:
Trying to do this in profile scripts assumes that you only run local
terminals that come from Fedora and that have been tested. For example,
if you SSH to a Fedora box from an old xterm that doesn't do 256 colors,
what happens if
Once upon a time, Matthew Garrett mj...@srcf.ucam.org said:
On Mon, Jun 25, 2012 at 08:47:16PM -0500, Chris Adams wrote:
Trying to do this in profile scripts assumes that you only run local
terminals that come from Fedora and that have been tested. For example,
if you SSH to a Fedora box
On Thursday 31 May 2012 02:20:26 Pádraig Brady wrote:
On 05/30/2012 04:16 PM, Marc Deop wrote:
On Wednesday 30 May 2012 10:04:49 Pádraig Brady wrote:
I've some notes about 256 colors here:
http://www.pixelbeat.org/docs/terminal_colours/#256
That information is mostly fine. There are
[snip]
What I'd do (I will do if you prefer) is to propose the feature at:
https://fedoraproject.org/wiki/Releases/18/FeatureList
That will both provide a todo list and allow voting on acceptance.
That sounds reasonable, +1 for me here! :)
This thread was to get the whole problem before
On 05/31/2012 11:09 AM, Marc Deop i Argemí wrote:
On Thursday 31 May 2012 02:20:26 Pádraig Brady wrote:
On 05/30/2012 04:16 PM, Marc Deop wrote:
On Wednesday 30 May 2012 10:04:49 Pádraig Brady wrote:
I've some notes about 256 colors here:
http://www.pixelbeat.org/docs/terminal_colours/#256
Hi there,
We are building a leading edge Operating System, but still use only 8bit colors
by default in our terminal (I don't know about KDE… I stay under
GNOME, gnome-term (xterm)).
This limit the colors of many applications like vim, screen, tmux, weechat…
As seen (quick but not exhaustive
On 05/30/2012 09:30 AM, Kévin Raymond wrote:
Hi there,
We are building a leading edge Operating System, but still use only 8bit
colors
by default in our terminal (I don't know about KDE… I stay under
GNOME, gnome-term (xterm)).
This limit the colors of many applications like vim, screen,
On 05/30/2012 04:16 PM, Marc Deop wrote:
On Wednesday 30 May 2012 10:04:49 Pádraig Brady wrote:
I've some notes about 256 colors here:
http://www.pixelbeat.org/docs/terminal_colours/#256
That information is mostly fine. There are some errors though (you say you
set your TERM variable in
24 matches
Mail list logo
