On Sun, Oct 25, 2009 at 01:51:33AM +0100, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 07:42:26PM -0400, Thomas Dickey wrote:
well... if you're using terminfo to tell the number of colors (256 for
example), it's a reasonably safe assumption that xterm supports both
the aixterm
On Sat, Oct 24, 2009 at 07:20:28PM +0200, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 12:49:31AM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color converts colours 8-15 into 90-97 which are an
extension designed to
On Sat, Oct 24, 2009 at 03:54:57PM -0400, Thomas Dickey wrote:
On Sat, Oct 24, 2009 at 07:20:28PM +0200, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 12:49:31AM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color
On Sat, Oct 24, 2009 at 10:11:30PM +0100, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 03:54:57PM -0400, Thomas Dickey wrote:
Since aixterm 16-colors are part of the default configuration settings,
it's reasonable to count on the controls being present.
I can't count on them being
On Sat, Oct 24, 2009 at 07:42:26PM -0400, Thomas Dickey wrote:
On Sat, Oct 24, 2009 at 10:11:30PM +0100, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 03:54:57PM -0400, Thomas Dickey wrote:
Since aixterm 16-colors are part of the default configuration settings,
it's reasonable to count
Hi
If you set TERM to anything aside from screen or screen-256color inside tmux
you will get screen corruption because applications will send the incorrect
escape sequences. This is not a bug.
The FAQ does not say that setting TERM to screen-256color will just work,
although it could probably be
Hi
Okay, I can see the problem.
$ TERM=screen-256color tput setaf 15|cat -v
^[[97m
$ TERM=xterm-256color tput setaf 15|cat -v
^[[38;5;15
It appears screen-256color converts colours 8-15 into 90-97 which are an
extension designed to allow bright colours without the bold attribute (bold
font).
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color converts colours 8-15 into 90-97 which are an
extension designed to allow bright colours without the bold attribute (bold
font).
Looking at xterm's ctlseqs.pdf, it refers to these 90-97 and 100-107
On Sat, Oct 24, 2009 at 12:49:31AM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color converts colours 8-15 into 90-97 which are an
extension designed to allow bright colours without the bold attribute (bold
font).
Package: tmux
Version: 1.0-1
Severity: normal
In /usr/share/doc/tmux/FAQ.gz, it is suggested that to get 256 color
terminal support all one needs to do is to set the default $TERM to
screen-256color and everything will Just Work; it seems this is not
actually the case.
Inside GNU screen,
Hi,
thanks for your report.
Am Montag 12 Oktober 2009 12:46:03 schrieb Screwtape:
Package: tmux
Version: 1.0-1
Severity: normal
In /usr/share/doc/tmux/FAQ.gz, it is suggested that to get 256 color
terminal support all one needs to do is to set the default $TERM to
screen-256color and
On Mon, Oct 12, 2009 at 01:14:49PM +0200, Karl Ferdinand Ebert wrote:
I could reproduce this behaviour but not the issue with mutt. Could you give
more detail on mutt's screen-corruption?
My problem was that with TERM=xterm-256color inside tmux, mutt would
draw rows at the wrong place as you
12 matches
Mail list logo
