On Tue, Aug 31, 2010 at 01:57:39PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7
Quoth Brian Cuttler on Wednesday, 01 September 2010:
On Tue, Aug 31, 2010 at 01:57:39PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is
Chip,
curie's mutt is built with slang, nnewton's is built with ncurses. That
probably accounts for the difference.
I finally got a download of a newer mutt version from sunfreeware
and will install it on the Solaris x86 platform.
Assuming that its also built with slang - do you know what I
Quoth Brian Cuttler on Wednesday, 01 September 2010:
Chip,
curie's mutt is built with slang, nnewton's is built with ncurses. That
probably accounts for the difference.
I finally got a download of a newer mutt version from sunfreeware
and will install it on the Solaris x86 platform.
Chip,
I installed mutt 1.5.20 from sunfreeware and found that we
where missing several required packages, including slang.
I installed and mutt seems to open my outbox ok, That is
the index displays correctly with header and footer inverse
and the index bar being visible.
Typically the outbox
Quoth Brian Cuttler on Wednesday, 01 September 2010:
Chip,
I installed mutt 1.5.20 from sunfreeware and found that we
where missing several required packages, including slang.
I installed and mutt seems to open my outbox ok, That is
the index displays correctly with header and footer
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Hate ask, but I think I've tried the obvious...
Moving from a Solaris 9/sparc box with mutt Mutt 1.4.1i (2003-03-19)
to Solaris 10x86 with Mutt 1.5.17 (2007-11-01) and I'm finding that
my colors and highlighting don't work at all.
Checked
Chip,
No, mutt is not producing any errors, its just failing, not only
to set colors but even to highlight (or is it simply reverse)
the black and white header and footer or provide inverse for the
message I'm currently pointing to in the index.
With mutt not complaining I'm guessing it is a
On Tue, Aug 31, 2010 at 01:56:01PM -0400, Brian Cuttler wrote:
Hate ask, but I think I've tried the obvious...
Moving from a Solaris 9/sparc box with mutt Mutt 1.4.1i (2003-03-19)
to Solaris 10x86 with Mutt 1.5.17 (2007-11-01) and I'm finding that
my colors and highlighting don't work at
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Chip,
No, mutt is not producing any errors, its just failing, not only
to set colors but even to highlight (or is it simply reverse)
the black and white header and footer or provide inverse for the
message I'm currently pointing to in the
Will,
I'd tried term vt100 and dtterm, setting both xterm and xterm-color
env vars I now get a black block cursor in the last column of the
index as I move up and down the message index.
looking more and more like a termcap issue... I'll see if there are
other vt100 or dtterm color settings as
Will,
Here is a crazy test. from the system I'd ssh'd into, I ssh'd
to a linux box where, the # ls command there has an option to
display different types of files in different colors. That worked
perfectly.
Term there was xterm and there was also the addtional env var
of COLORTERM set to 1.
By
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that the errors will tells someone who
is not me where the
Quoth Brian Cuttler on Tuesday, 31 August 2010:
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that
Chip,
This works a little better
# echo `tput setaf 1`hello`tput me`
tput: unknown terminfo capability 'me'
hello
Where we are in red from hello onwards.
So there are some colors available.
On Tue, Aug 31, 2010 at 11:46:57AM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31
Quoth Brian Cuttler on Tuesday, 31 August 2010:
Chip,
This works a little better
# echo `tput setaf 1`hello`tput me`
tput: unknown terminfo capability 'me'
hello
Where we are in red from hello onwards.
So there are some colors available.
On Tue, Aug 31, 2010 at 11:46:57AM -0700,
On Tue, Aug 31, 2010 at 02:54:39PM -0400, Brian Cuttler wrote:
Will,
Here is a crazy test. from the system I'd ssh'd into, I ssh'd
to a linux box where, the # ls command there has an option to
display different types of files in different colors. That worked
perfectly.
Term there was
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8 colors, that is
Black, Red, Green, Yellow, Blue, Magenta, Cyan, White (on white...)
When run on my Solaris 10 desktop I then get
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8 colors, that is
Black, Red, Green, Yellow, Blue, Magenta, Cyan, White
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf ${color}``date`
done
output is as expected for the first 8
Quoth Brian Cuttler on Tuesday, 31 August 2010:
From Chip Camden
Try this at a shell prompt:
echo `tput AF 1`hello`tput me`
hello should be in red.
Chip - B/W only, plus the errors. I'm guessing that the
errors tell us where the root of the problem is.
Ok, I'm guessing that
Quoth Brian Cuttler on Tuesday, 31 August 2010:
On Tue, Aug 31, 2010 at 01:16:03PM -0700, Chip Camden wrote:
Quoth Brian Cuttler on Tuesday, 31 August 2010:
This is telling...
#!/bin/sh
for color in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0
do
echo `tput setaf
May I suggest that trimming some of the quoted material in these
messages? It'd make it easier to read the thread, and maybe help out.
Nico
--
BTW, I use screen in gnome-terminal.
I notice the following:
- TERM is screen-bce;
- VIM works fine, handles colors;
- Mutt built with S-Lang does not start unless I set TERM to xterm or
xterm-color; Mutt complains that Key sequence is too long,
SLcurses_initscr: init failed;
- If I
Quoth Nicolas Williams on Tuesday, 31 August 2010:
BTW, I use screen in gnome-terminal.
I notice the following:
- TERM is screen-bce;
- VIM works fine, handles colors;
- Mutt built with S-Lang does not start unless I set TERM to xterm or
xterm-color; Mutt complains that Key
On Tue, Aug 31, 2010 at 02:37:48PM -0700, Chip Camden wrote:
You could probably get mutt to start with TERM=screen-bce is termcap has
an appropriate entry for it. I found that even though mutt with slang
uses terminfo, it queries termcap on startup.
screen(1) does set TERMCAP in the
26 matches
Mail list logo
