Re: mutt - color problem
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 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 the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a terminal/display
issue rather than a mutt issue, just hadn't realized that the
new
server (since nothing changed on my desktop) had, ya know,
issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config
changes,
just # ssh'd into a different server. My desktop is Solaris
10x86
and that hasn't changed either. Its something with the
server or
with the specific build of mutt, I believe both from
sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your
help,
Brian
---
Brian R Cuttler
brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may
contain
confidential or sensitive information which is, or may be,
legally
privileged or otherwise protected by law from further
disclosure. It
is intended only for the addressee. If you received this
in error or
from someone who was not authorized to send it to you,
please do not
distribute, copy or use it or any attachments. Please
notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough
about Solaris
to help you, but I can tell you that on FreeBSD I ran into
several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly
in *both*
termcap and terminfo. Specifically, it needs to have the
correct number
of colors specified (Co# in termcap) and the correct
sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my
case) has to
be built with the same color options (256 color support, in
my case).
So, what kind of problem are you seeing? Is mutt
Re: mutt - color problem
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 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 the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a
terminal/display
issue rather than a mutt issue, just hadn't realized that the
new
server (since nothing changed on my desktop) had, ya know,
issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the
download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config
changes,
just # ssh'd into a different server. My desktop is
Solaris 10x86
and that hasn't changed either. Its something with the
server or
with the specific build of mutt, I believe both from
sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your
help,
Brian
---
Brian R Cuttler
brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may
contain
confidential or sensitive information which is, or may
be, legally
privileged or otherwise protected by law from further
disclosure. It
is intended only for the addressee. If you received this
in error or
from someone who was not authorized to send it to you,
please do not
distribute, copy or use it or any attachments. Please
notify the
sender immediately by reply e-mail and delete this from
your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough
about Solaris
to help you, but I can tell you that on FreeBSD I ran into
several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly
in *both*
termcap and terminfo. Specifically, it needs to have the
correct number
of colors specified (Co# in termcap) and the correct
sequences for
setting foreground/background color.
3. The terminal in
Re: mutt - color problem
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 need to do to make it work ? thanks, Brian IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: mutt - color problem
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. Assuming that its also built with slang - do you know what I need to do to make it work ? thanks, Brian The version I'm using is built with slang, and colors work here (a full 256 of them). Give it a try and we'll take it from there. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp7jMykPHeZm.pgp Description: PGP signature
Re: mutt - color problem
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 does not show messages based on my color highlighting rules, but based on prior behavor things are looking good. I ran into what I suspect is a syntax error with the inbox when I invoke mutt with no arguments. Bad IDN imaps.wadsworth.org. .muttrc file beings this way. [curie] ~ 233 more .muttrc set spoolfile=imap://imaps.wadsworth.org/INBOX set folder=imap://imaps.wadsworth.org/ I'm looking online now, don't know for sure that the error is where I'm looking (or what IDN stands for) but the .muttrc file is static and works under v1.5.17 (prior version on solaris x86) and 1.4.1i on Solaris sparc. thanks, Brian IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: mutt - color problem
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 inverse and the index bar being visible. Typically the outbox does not show messages based on my color highlighting rules, but based on prior behavor things are looking good. I ran into what I suspect is a syntax error with the inbox when I invoke mutt with no arguments. Bad IDN imaps.wadsworth.org. .muttrc file beings this way. [curie] ~ 233 more .muttrc set spoolfile=imap://imaps.wadsworth.org/INBOX set folder=imap://imaps.wadsworth.org/ I'm looking online now, don't know for sure that the error is where I'm looking (or what IDN stands for) but the .muttrc file is static and works under v1.5.17 (prior version on solaris x86) and 1.4.1i on Solaris sparc. thanks, Brian I have no experience with IMAP, so others will need to help you there. Glad to hear that the screen attributes are working properly, though. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpPYAgiqQjGS.pgp Description: PGP signature
Re: mutt - color problem
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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp3ieSYHRdBK.pgp Description: PGP signature
Re: mutt - color problem
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 terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: mutt - color problem
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 all. Checked terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. When you ssh in to the server what does: env|grep TERM output? If the TERM is xterm, perhaps also exporting COLORTERM=xterm-color will help. -- Will Fiveash
Re: mutt - color problem
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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me` hello should be in red. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpnWVqxZ6x8o.pgp Description: PGP signature
Re: mutt - color problem
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 well. thanks, Brian On Tue, Aug 31, 2010 at 01:40:39PM -0500, Will Fiveash wrote: 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 all. Checked terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. When you ssh in to the server what does: env|grep TERM output? If the TERM is xterm, perhaps also exporting COLORTERM=xterm-color will help. -- Will Fiveash --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: mutt - color problem
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 using # ssh -X, and then # ssh -X again I'm avoiding the termcap settings in the intermediate host though, aren't I ? For a test like that the middle man's problems are simply ignored. right ? On Tue, Aug 31, 2010 at 01:40:39PM -0500, Will Fiveash wrote: 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 all. Checked terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. When you ssh in to the server what does: env|grep TERM output? If the TERM is xterm, perhaps also exporting COLORTERM=xterm-color will help. -- Will Fiveash --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: mutt - color problem
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 error lies. [curie] ~ 212 printenv | grep TER TERM=xterm COLORTERM=1 [curie] ~ 213 echo `tput AF 1`hello`tput me` tput: unknown terminfo capability 'AF' tput: unknown terminfo capability 'me' hello On Tue, Aug 31, 2010 at 11:46:57AM -0700, Chip Camden wrote: 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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me` hello should be in red. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com|
Re: mutt - color problem
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 the errors will tells someone who is not me where the error lies. [curie] ~ 212 printenv | grep TER TERM=xterm COLORTERM=1 [curie] ~ 213 echo `tput AF 1`hello`tput me` tput: unknown terminfo capability 'AF' tput: unknown terminfo capability 'me' hello On Tue, Aug 31, 2010 at 11:46:57AM -0700, Chip Camden wrote: 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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me`
Re: mutt - color problem
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 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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me` hello should be in red. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any
Re: mutt - color problem
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, Chip Camden wrote: 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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me` hello should be in red. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518
Re: mutt - color problem
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 xterm and there was also the addtional env var of COLORTERM set to 1. By using # ssh -X, and then # ssh -X again I'm avoiding the termcap settings in the intermediate host though, aren't I ? For a test like that the middle man's problems are simply ignored. right ? Beyond my guessing about COLORTERM I'm not sure what the problem is. You may want to look at the terminfo.4 man page and the See Also pages. I used to run Solaris 10 and used a version of mutt that I built myself that was using slang instead of curses (not sure why at this point). These days I'm running a internal developer build of Solaris which has a native version of libncurses so I've compiled the latest developer version of mutt to use that. Here are the shared libs that mutt is currently linked to: libncurses.so.5 = /usr/gnu/lib/libncurses.so.5 libssl.so.0.9.8 = /lib/libssl.so.0.9.8 libcrypto.so.0.9.8 =/lib/libcrypto.so.0.9.8 libz.so.1 = /lib/libz.so.1 libsasl.so.1 = /usr/lib/libsasl.so.1 libgdbm.so.3 = /usr/lib/libgdbm.so.3 libidn.so.11 = /usr/lib/libidn.so.11 libsocket.so.1 =/lib/libsocket.so.1 libnsl.so.1 = /lib/libnsl.so.1 libc.so.1 = /lib/libc.so.1 libmd.so.1 =/lib/libmd.so.1 libmp.so.2 =/lib/libmp.so.2 libm.so.2 = /lib/libm.so.2 My TERM is xterm when I ssh into a Solaris system. Note that I do not have to set COLORTERM in order to have mutt display color. I have a shell script wrapper for mutt so it can find the /usr/gnu/lib/libncurses.so.5 lib. It basically looks like: #!/usr/bin/ksh -p export LD_LIBRARY_PATH=/usr/gnu/lib exec $HOME/bin/$(uname -p)/mutt $@ # end of script I have the binary version of mutt in $HOME/bin/i386/ -- Will Fiveash
Re: mutt - color problem
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 the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a terminal/display
issue rather than a mutt issue, just hadn't realized that the new
server (since nothing changed on my desktop) had, ya know, issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config changes,
just # ssh'd into a different server. My desktop is Solaris 10x86
and that hasn't changed either. Its something with the server or
with the specific build of mutt, I believe both from sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your help,
Brian
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.
It
is intended only for the addressee. If you received this in error
or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough about
Solaris
to help you, but I can tell you that on FreeBSD I ran into several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly in *both*
termcap and terminfo. Specifically, it needs to have the correct
number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case) has
to
be built with the same color options (256 color support, in my case).
So, what kind of problem are you seeing? Is mutt complaining, or is
it
just silently not changing the colors?
--
Sterling (Chip) Camden| sterl...@camdensoftware.com |
2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com|
http://chipsquips.com
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized
Re: mutt - color problem
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 white...)
When run on my Solaris 10 desktop I then get the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a terminal/display
issue rather than a mutt issue, just hadn't realized that the new
server (since nothing changed on my desktop) had, ya know, issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config changes,
just # ssh'd into a different server. My desktop is Solaris 10x86
and that hasn't changed either. Its something with the server or
with the specific build of mutt, I believe both from sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your help,
Brian
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.
It
is intended only for the addressee. If you received this in
error or
from someone who was not authorized to send it to you, please do
not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough about
Solaris
to help you, but I can tell you that on FreeBSD I ran into several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly in
*both*
termcap and terminfo. Specifically, it needs to have the correct
number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case)
has to
be built with the same color options (256 color support, in my
case).
So, what kind of problem are you seeing? Is mutt complaining, or
is it
just silently not changing the colors?
--
Sterling (Chip) Camden| sterl...@camdensoftware.com |
2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com|
http://chipsquips.com
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which
Re: mutt - color problem
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 colors, that is
Black, Red, Green, Yellow, Blue, Magenta, Cyan, White (on white...)
When run on my Solaris 10 desktop I then get the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a terminal/display
issue rather than a mutt issue, just hadn't realized that the new
server (since nothing changed on my desktop) had, ya know, issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config changes,
just # ssh'd into a different server. My desktop is Solaris
10x86
and that hasn't changed either. Its something with the server or
with the specific build of mutt, I believe both from
sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your
help,
Brian
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be,
legally
privileged or otherwise protected by law from further
disclosure. It
is intended only for the addressee. If you received this in
error or
from someone who was not authorized to send it to you, please
do not
distribute, copy or use it or any attachments. Please notify
the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough about
Solaris
to help you, but I can tell you that on FreeBSD I ran into several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly in
*both*
termcap and terminfo. Specifically, it needs to have the correct
number
of colors specified (Co# in termcap) and the correct sequences for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my case)
has to
be built with the same color options (256 color support, in my
case).
So, what kind of problem are you seeing? Is mutt complaining, or
is it
just silently not changing the colors?
--
Sterling (Chip) Camden| sterl...@camdensoftware.com |
2048D/3A978E4F
http://camdensoftware.com | http://chipstips.com|
http://chipsquips.com
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Re: mutt - color problem
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 the errors will tells someone who is not me where the error lies. [curie] ~ 212 printenv | grep TER TERM=xterm COLORTERM=1 [curie] ~ 213 echo `tput AF 1`hello`tput me` tput: unknown terminfo capability 'AF' tput: unknown terminfo capability 'me' hello On Tue, Aug 31, 2010 at 11:46:57AM -0700, Chip Camden wrote: 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 index. With mutt not complaining I'm guessing it is a terminal/display issue rather than a mutt issue, just hadn't realized that the new server (since nothing changed on my desktop) had, ya know, issues. I don't think its mutt, I think mutt is just a symptom, had hoped that everything would work out of the box. Trying to download newer sunfreeware mutt build but the download keeps stalling out on me. thanks, Brian On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote: 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 terminal type, the same, didn't make any config changes, just # ssh'd into a different server. My desktop is Solaris 10x86 and that hasn't changed either. Its something with the server or with the specific build of mutt, I believe both from sunfreeware. Sorry to ask such a rudimenary question. Thanks for your help, Brian --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Rudimentary, yes. Easy, no. I probably don't know enough about Solaris to help you, but I can tell you that on FreeBSD I ran into several issues: 1. I had to build mutt with slang instead of ncurses. 2. The terminal definition I use has to be set up correctly in *both* termcap and terminfo. Specifically, it needs to have the correct number of colors specified (Co# in termcap) and the correct sequences for setting foreground/background color. 3. The terminal in which you are running mutt (urxvt in my case) has to be built with the same color options (256 color support, in my case). So, what kind of problem are you seeing? Is mutt complaining, or is it just silently not changing the colors? -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation. Try this at a shell prompt: echo `tput AF 1`hello`tput me`
Re: mutt - color problem
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 ${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 the inverse for the
last 8. I do not get the inverse on the remote system.
On Tue, Aug 31, 2010 at 12:22:00PM -0700, Chip Camden wrote:
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, Chip Camden wrote:
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 index.
With mutt not complaining I'm guessing it is a terminal/display
issue rather than a mutt issue, just hadn't realized that the new
server (since nothing changed on my desktop) had, ya know, issues.
I don't think its mutt, I think mutt is just a symptom, had
hoped that everything would work out of the box.
Trying to download newer sunfreeware mutt build but the download
keeps stalling out on me.
thanks,
Brian
On Tue, Aug 31, 2010 at 11:19:59AM -0700, Chip Camden wrote:
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 terminal type, the same, didn't make any config
changes,
just # ssh'd into a different server. My desktop is Solaris
10x86
and that hasn't changed either. Its something with the server
or
with the specific build of mutt, I believe both from
sunfreeware.
Sorry to ask such a rudimenary question.
Thanks for your
help,
Brian
---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be,
legally
privileged or otherwise protected by law from further
disclosure. It
is intended only for the addressee. If you received this in
error or
from someone who was not authorized to send it to you, please
do not
distribute, copy or use it or any attachments. Please notify
the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Rudimentary, yes. Easy, no. I probably don't know enough
about Solaris
to help you, but I can tell you that on FreeBSD I ran into
several
issues:
1. I had to build mutt with slang instead of ncurses.
2. The terminal definition I use has to be set up correctly in
*both*
termcap and terminfo. Specifically, it needs to have the
correct number
of colors specified (Co# in termcap) and the correct sequences
for
setting foreground/background color.
3. The terminal in which you are running mutt (urxvt in my
case) has to
be built with the same color options (256 color support, in my
case).
So, what kind of problem are you seeing? Is mutt complaining,
or is it
just silently not changing the colors?
--
Sterling (Chip) Camden| sterl...@camdensoftware.com |
2048D/3A978E4F
http://camdensoftware.com |
Re: mutt - color problem
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 --
Re: mutt - color problem
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 set TERM=xterm then VIM thinks the terminal is monochrome; - If I set TERM=xterm then Mutt does produce colors; - If I set TERM=xterm-color then both, VIM and Mutt handle color. Weird, no? This is almost certainly a result of using different APIs (VIM uses curses, Mutt uses S-Lang). I believe my colleague Will F. has shown that Mutt works fine with curses (ncurses). This is all on Solaris. Nico --
Re: mutt - color problem
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 sequence is too long, SLcurses_initscr: init failed; - If I set TERM=xterm then VIM thinks the terminal is monochrome; - If I set TERM=xterm then Mutt does produce colors; - If I set TERM=xterm-color then both, VIM and Mutt handle color. Weird, no? This is almost certainly a result of using different APIs (VIM uses curses, Mutt uses S-Lang). I believe my colleague Will F. has shown that Mutt works fine with curses (ncurses). This is all on Solaris. Nico -- 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. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgpmauqYnEsg1.pgp Description: PGP signature
Re: mutt - color problem
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 environment... There is a termcap entry for screen, but not for screen-bce. If I add the screen-bce entry I still get the same error, as I do if I set TERM=screen. Aha! I must unset TERMCAP to make Mutt/S-Lang happy. Nico --
Re: Color problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, June 2 at 08:08 PM, quoth Ken Weingold: I hope I can explain this well. I just built mutt 1.5.19 after using 1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19 was compiled using ncurses 5.6 (5.4 is also available). I have new mail in bold cyan. In 1.5.19, if I scroll the indicator up over the new emails, it unbolds them. Scrolling down over them will make them bold again. Any idea why this is happening? Do you mean that they're un-bolded while the indicator is highlighting them? Or do you mean that they're un-bolded only if the indicator is higher up on the list than they are and that when the indicator is lower in the list they become bolded again? If it's the former, then that's expected behavior (unfortunately) - the indicator bar isn't supposed to preserve *any* of the underlying index formatting. If the latter... that sounds like a bug. Try reporting it to mutt-dev and see if they have any ideas (my first guess would be to make sure it's linking against the version of ncurses that you think it is, e.g. with the ldd tool). ~Kyle - -- He that never changes his opinions, never corrects his mistakes, will never be wiser on the morrow than he is today. -- Tryon Edwards -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKJpHRAAoJECuveozR/AWeXJgQAIxuF5cl4BptBX1001LSBDXH xrDsi5pfpXjbjpjJTUUgZyEYAkNhCuX3FJR43OKI9HP9E4TXW2Y0BHsZqnGRicXn 9c4L87SJMQdns4IXjm56J5YbnTJO5aLBi3VfVMkDx31VP1SYUbT504DiYEpAlzyv qjLIav7IcHXmnlWDhX/mj2bpWoP5mtdtE+aohFekBmxQTMQdyaR5ZmyI8h/QtAI3 2eJ+ceh180tkkESw0hyXQObDyFSh2h6dbDg3Qsniqy5I7nmLI6fnjMdyWaO2Np8V EI5Xjvx0ElQABrK7NLk3XR+wqWoJo3VFzMIpFYgul4v9hNvLtnrhwFvt+xatNRzF exd17N7ZCmSXHVgiOqipkEw1pkyb9cAanHKljiUQ5Zdy74DRdd7eVRmW5QS91t+E Mop4FYdKStqx3FpJ9JikvxkBufOi3QoGu917Q3NUYFpLRcYUQ4wt9c/h+VNJyFv+ 2YiR8/pVH1abN6Ch2bFqDyLhBLUot8FCQeFO+3Bz7IKAfoUqJRkkEuTgQFlxVjRp HLzf/LopND/ja8su7sZT/qJGUb2xLJtU9YP1ICuUPZ498z9jmnOZlhVTX2TKCvvl 15TPmPNLqMnCoJIAKMel7hGxY9nDVOaMml6aSJ8M1e0InpLqwts7U32TTkGmFkX1 W3E832wAi8d23qrU4VTJ =ma0x -END PGP SIGNATURE-
Re: Color problem
On Wed, Jun 3, 2009, Kyle Wheeler wrote: On Tuesday, June 2 at 08:08 PM, quoth Ken Weingold: I hope I can explain this well. I just built mutt 1.5.19 after using 1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19 was compiled using ncurses 5.6 (5.4 is also available). I have new mail in bold cyan. In 1.5.19, if I scroll the indicator up over the new emails, it unbolds them. Scrolling down over them will make them bold again. Any idea why this is happening? Do you mean that they're un-bolded while the indicator is highlighting them? Or do you mean that they're un-bolded only if the indicator is higher up on the list than they are and that when the indicator is lower in the list they become bolded again? It's actually when I move the indicator bar over them. If I jump straight to the top of the index, the boldness doesn't get affected. I do know it's compiling with the correct version of ncurses from 'mutt -v's output. Or could that not be correct? -Ken
Re: Color problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, June 3 at 11:18 AM, quoth Ken Weingold: Do you mean that they're un-bolded while the indicator is highlighting them? Or do you mean that they're un-bolded only if the indicator is higher up on the list than they are and that when the indicator is lower in the list they become bolded again? It's actually when I move the indicator bar over them. If I jump straight to the top of the index, the boldness doesn't get affected. I do know it's compiling with the correct version of ncurses from 'mutt -v's output. Or could that not be correct? What it's compiling against and what it's linking against could be two different things. Mutt gets the version number from the ncurses header files; but it's quite possible that those headers are mis-matched to the library that was actually used to link against. Assuming you don't know: compiling most large software (like mutt) is a two-step process. First, each source file (e.g. a .c file) is compiled into an object file (a .o file), then the object files are linked together along with any libraries that are needed to create an executable binary (the program itself). People who have multiple versions of any given library often get themselves into trouble by compiling with headers that don't match the libraries. For example, you could compile against version 2.6 and then link against 2.4. The program would think it was using 2.6, but since it was linked against 2.4, would run into weirdness. This isn't a problem for people who only ever have a single version of any given library available. ~Kyle - -- I would therefore like to posit that computing's central challenge, how not to make a mess of it, has not yet been met. -- Edsger Dijkstra -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKJpacAAoJECuveozR/AWeBpIP/RNnEWwgmnfnk76xncqTWxsH v8r2bj9GhTPP2sOoCmTspjl2PuPBp36LmkMuowZeXu2otEUsSNNtinvAeo2GV8Ev +UWW3kdPr8fOnSLK6veeumpa/u1aVuYshGGxrq37sQnMEvssN72kkLPOHAd5CaxD uprnqdDeFyMzkkIsp5kd3bkrvM9Knr1TcaRFp1RAgCCQeEbQR1ZrPKZZqWjBdgub 7VQhKo6AUdvyfssiSlb2zPXSqcSXPgPpVzBbjEPRSC1IH3M3Xoh2Qf8czHNJxQ4P uhy0saW9fAkeKinUL2XpcWiNsCV3NOPIpE1Op2mRSz5GkptIHnteCRkhzU9Rw3Hb 6RvtJsvm5/yYwNZGDJ6EG+co/wo5+x1jt0KT1UkQLjooltOUPRLyETRKKc3dDtrx 6JbI/qncG9Ga9LoaeCbbTtSSiA95xp1EyvqsaApyGp7DjbQpcnpxlKvf8u78TcLD N/G7UuczfYjIpkZvdrLJ/PntW0/6Sgbf1uqD+1TYo4dNc78/YyDHcxVaZTSjTiCe yGxfyFpjgvcaHkK87N1w6i94YPohd4wQ9n+wy3fHASnjZu3hc/nvEb56Qes77ben 3CVh119/mtkA2a+S9+nciDhaX1ZwuBLsvDw6N8IA6RdQpTeNlOp0oFaFwjXuMrYu uX1jBBzHS0mC3QY6gSUm =sH9V -END PGP SIGNATURE-
Re: Color problem
On Wed, Jun 3, 2009, Kyle Wheeler wrote: What it's compiling against and what it's linking against could be two different things. Mutt gets the version number from the ncurses header files; but it's quite possible that those headers are mis-matched to the library that was actually used to link against. Assuming you don't know: compiling most large software (like mutt) is a two-step process. First, each source file (e.g. a .c file) is compiled into an object file (a .o file), then the object files are linked together along with any libraries that are needed to create an executable binary (the program itself). People who have multiple versions of any given library often get themselves into trouble by compiling with headers that don't match the libraries. For example, you could compile against version 2.6 and then link against 2.4. The program would think it was using 2.6, but since it was linked against 2.4, would run into weirdness. Ah, crap. :) This on panix.com servers. I used --with-curses=/usr/local/ncurses-5.6 They are really good, so I assume it is correct. There is also an ncurses-5.4 install under /usr/local. Either way, there is a patch I used for the last version of mutt I was using, 1.5.10. 5patch-1.5.1.nr.indicator_not_bright. This was to make any text under the indicator bar not bold. It still works, and interestintly enough, also fixes this issue. -Ken
Re: Color problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, June 3 at 11:36 AM, quoth Ken Weingold: Ah, crap. :) This on panix.com servers. I used --with-curses=/usr/local/ncurses-5.6 They are really good, so I assume it is correct. There is also an ncurses-5.4 install under /usr/local. That should do it, unless there are runtime LD_LIBRARY_PATH or LD_PRELOAD issues. Either way, there is a patch I used for the last version of mutt I was using, 1.5.10. 5patch-1.5.1.nr.indicator_not_bright. This was to make any text under the indicator bar not bold. It still works, and interestintly enough, also fixes this issue. Ahhh. You may want to post that patch to the mutt-dev team. If it really fixes a bug, they'll probably be interested in it. ~Kyle - -- I am certain there is too much certainty in the world. -- Michael Crichton, State of Fear -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKJpvqAAoJECuveozR/AWe1k0P/igdfsAVa72pbu0JycLCIJS1 JnTDUtnlKPhMpQP7E4TCHvmm4N9MN6XpKTGHEJNsfqHB2Odgl1TVHZuBIYYA9G2K W/lqVZaqSkZBViXs6+gbNPFxzsJkQMG0R4Z6ZnfQDqPZP/7tQyGG0WKEAg420a1Q v+IZOeoeRpy5WjQTEGcaI301oDsF0njYECZxkuqG+QI17nu32Q0xdJU8E0JdH9Bm zOse7Jt9i2cJH8QtzEF8Y0Zsv/rCQeJFJ46OlwBdBVOLT3M1kbyS7aliO/gKmEMT i1H+QbyrvJNl89UVOkLWkF9m12gaQdP7z9dT3TbjTrakelcHQE6j9oem8LgBClxF Aenv8ZJqe0AfDTb0qoQEkEAoX/kMBdLoi72FLIsaeHIKOr9kkRw8V+FSLozje8lF 8atAp7HU02vrwFLvPcerCVbz9zgM2zVra/oODX2fcZTTtsIS5fe8valB0KLwb1OQ Oec/Z5A+IXun/+eYyx9g6YeAhlqS6FHEXuNg6c9JMIvfjSPKbSL+zBycFJb05/GI D6kiFrJZ/peBZHRBnnVF1O8r1zC+cjxCCpw2I6NnyGv4i49ARjT5vsfdtWm0EtvK LJ78ISROGVZloFa/pgvY9e5XG4K8RC4S5VINgQCdOHA9q/OlFwV5UQYc6Zw724zl bCLg87RLQ11KANGhgOKj =MpDJ -END PGP SIGNATURE-
Re: Color problem
On Wed, Jun 3, 2009, Kyle Wheeler wrote: Either way, there is a patch I used for the last version of mutt I was using, 1.5.10. 5patch-1.5.1.nr.indicator_not_bright. This was to make any text under the indicator bar not bold. It still works, and interestintly enough, also fixes this issue. Ahhh. You may want to post that patch to the mutt-dev team. If it really fixes a bug, they'll probably be interested in it. Will do. Thanks. -Ken
Color problem
I hope I can explain this well. I just built mutt 1.5.19 after using 1.5.10 for quite a long time. 1.5.10 was using ncurses 5.2 and 1.5.19 was compiled using ncurses 5.6 (5.4 is also available). I have new mail in bold cyan. In 1.5.19, if I scroll the indicator up over the new emails, it unbolds them. Scrolling down over them will make them bold again. Any idea why this is happening? Thanks. -Ken
Re: Color problem for mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday, April 18 at 10:27 AM, quoth He Wen: i wanna know how to highlight a specific field of a index item, for example, the date field? There's no good way, unfortunately. There may be a patch out there somewhere that allows you to do it, but in standard mutt... nope. I thought that maybe you could do it by changing your $index_format to include color-changing commands... but that gets passed through iconv (apparently), so the ansi color commands get masked out by question marks. ~Kyle - -- Victory goes to the player who makes the next-to-last mistake. -- Chessmaster Savielly Gricorievitch Tatrtak -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAknqGPkACgkQBkIOoMqOI17C4gCgyxyJqBsbMDNILBDYLtqc9kgM fZoAnjruMjvxe12g33/lXhJ7Vq56YJXf =GgtR -END PGP SIGNATURE-
Re: Color problem for mutt
Hi, * He Wen schrieb am Samstag, den 18. April 2009: i wanna know how to highlight a specific field of a index item, for example, the date field? Here is the Indexcolor Patch: http://greek0.net/mutt.html Andreas
Color problem for mutt
Hi you guys! i wanna know how to highlight a specific field of a index item, for example, the date field? Thanks :-) -- He Wen School of Electrical Engineering Computer Science, Peking University Beijing, 100871 China
Re: color problem - worked around
I'll have to try building 1.3.23i and see if I can spot the problem (when I'm at home). I did build one or two of the 1.3.x series, but just to check on progress... setting the color of the normal object to have a default background makes all the difference. it is not even necessary to set the body attribute unless you want a different foreground color. thanks for all the tips guys (when in doubt, rtfm) aloha, dave msg21027/pgp0.pgp Description: PGP signature
THANKS FOR: VIM (color) problem when used within mutt
Lou, I am happily repling to your message in the mutt editor, with properly colored quotes and all, after replacing the mutt_vim_rc file with the one you sent yesterday. Thanks again!, Marco On 2001/07/10 20:18:20 -0400, Louis LeBlanc wrote: I thought that file looked familiar. One problem with it. You must have emacs set to autoreplace tabs or something. The trailing whitespace could be from doing a cut and paste, though. I fixed your file by putting tabs back where they belong (tabs are often a pain in the nexk when you work on code, but for regexps and some config files, they are critical). Here is the diff between yours (after I fixed it) and the one I use: $ diff muttvimrc .mutt/mail.vim 1d0 75c74 order is important here! --- order is imporant here! 83,84c82,83 hi link mailHeaderKey Red hi link mailHeaderBlue --- hi link mailHeaderKey Green hi link mailHeaderCyan 86c85 hi link mailQuoted2 LightBlue --- hi link mailQuoted2 Cyan Pretty close. I do remember posting this a while back, and maybe I did the bad thing and just did a copy/paste. If so, my fault you had a hard time. This is actually a modified version of the one Felix von Leitner wrote. His version is actually included with the Vim dist. and can be found at /usr/share/vim/vim57/syntax/mail.vim (at least on RH6.2) In order to avoid further tab confusion, I am bzipping your repaired muttvimrc back up and attaching it that way. HTH Lou On 07/10/01 11:45 PM, Marco Fioretti sat at the `puter and typed: Hello, Some days ago, I asked for help on this list because I couldn't stand the colors appearing in vim/mutt when replying to messages. Several people explained how to fix this behavior. I'd like first of all to thank them, especially Felix von Leitner, for providing many useful suggestions. Eventually I set: set editor = /usr/bin/vim -c '/^$/+1' -u '~/.mutt_vim.rc' where mutt_vim_rc is the file attached to this message. Now colors are wonderful, but: 1) when I reply to message, I see an error message flash in the mutt window, too quick to read it. 2) vim behaves strangely: it doesn't react to the backspace key, or to the back arrow key, for example. Running from the command line vim -s .mutt_vim.rc doesn't produce any visible error. Any clues, or suggestions on how to capture the flashing error message? The only thing I can see weird in that file is that, having pasted it from the mutt window to an emacs buffer, it ended up with MANY blank spaces at the end of each line... TIA, Marco Fioretti -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: THANKS FOR: VIM (color) problem when used within mutt
On 07/11/01 07:32 PM, Marco Fioretti sat at the `puter and typed: Lou, I am happily repling to your message in the mutt editor, with properly colored quotes and all, after replacing the mutt_vim_rc file with the one you sent yesterday. Thanks again!, Marco Glad to help. L -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: ssh and default bg color problem
On Tue, Dec 26, 2000 at 01:00:28PM -0500, Thomas Dickey wrote: On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote: I currently run mutt in two different situations: 1. on my home machine (linux) in a transparent Eterm window 2. ssh-ing into my home machine from a Windows box. Same for me, I just do 'export TERM=linux" and it works fine. -- Virginie Vacca LUG Parinux http://www.parinux.org
Re: ssh and default bg color problem
On Fri, Jan 05, 2001 at 06:30:53PM +0100, Virginie wrote:
On Tue, Dec 26, 2000 at 01:00:28PM -0500, Thomas Dickey wrote:
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote:
I currently run mutt in two different situations:
1. on my home machine (linux) in a transparent Eterm window
2. ssh-ing into my home machine from a Windows box.
Same for me, I just do 'export TERM=linux" and it works fine.
comparing linux to Eterm.
comparing booleans.
bw: F:T.
km: F:T.
mc5i: F:T.
comparing numbers.
btns: NULL, 5.
cols: NULL, 80.
lines: NULL, 24.
lm: NULL, 0.
ncv: 18, NULL.
comparing strings.
acsc:
'+\020\,\021-\030.^Y0\333`\004a\261f\370g\361h\260i\316j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330}\234~\376',
'``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~'.
civis: '\E[?25l\E[?1c', '\E[?25l'.
clear: '\E[H\E[J', '\E[H\E[2J'.
cnorm: '\E[?25h\E[?0c', '\E[?25h'.
cub: NULL, '\E[%p1%dD'.
cud: NULL, '\E[%p1%dB'.
cud1: '^J', '\E[B'.
cuf: NULL, '\E[%p1%dC'.
cuu: NULL, '\E[%p1%dA'.
cvvis: '\E[?25h\E[?8c', NULL.
dim: '\E[2m', NULL.
enacs: NULL, '\E)0'.
flash: '\E[?5h\E[?5l$200/', '\E[?5h\E[?5l'.
invis: '\E[8m', NULL.
is1: NULL, '\E[?47l\E\E[?1l'.
is2: NULL, '\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l'.
kDC: NULL, '\E[3$'.
kEND: NULL, '\E[8$'.
kHOM: NULL, '\E[7$'.
kLFT: NULL, '\E[d'.
kNXT: NULL, '\E[6$'.
kPRV: NULL, '\E[5$'.
kRIT: NULL, '\E[c'.
ka1: NULL, '\E[7~'.
ka3: NULL, '\E[5~'.
kb2: '\E[G', '\EOu'.
kbeg: NULL, '\EOu'.
kbs: '\177', '^H'.
kc1: NULL, '\E[8~'.
kc3: NULL, '\E[6~'.
kel: NULL, '\E[8\^'.
kend: '\E[4~', '\E[8~'.
kent: NULL, '\EOM'.
kf1: '\E[[A', '\E[11~'.
kf2: '\E[[B', '\E[12~'.
kf3: '\E[[C', '\E[13~'.
kf4: '\E[[D', '\E[14~'.
kf5: '\E[[E', '\E[15~'.
kfnd: NULL, '\E[1~'.
khlp: NULL, '\E[28~'.
khome: '\E[1~', '\E[7~'.
kslt: NULL, '\E[4~'.
kspd: '^Z', NULL.
mc4: NULL, '\E[4i'.
mc5: NULL, '\E[5i'.
nel: '^M^J', NULL.
rmacs: '\E[10m', '^O'.
rmam: NULL, '\E[?7l'.
rmcup: NULL, '\E[2J\E[?47l\E8'.
rmkx: NULL, ''.
rmpch: '\E[10m', NULL.
rs1: '\Ec\E]R', '\E\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H'.
rs2: NULL, '\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l\E'.
sgr:
'\E[0;10%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p5%t;2%;%?%p6%t;1%;%?%p7%t;8%;%?%p9%t;11%;m',
'\E[0%?%p1%p6%|%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;m%?%p9%t\016%e\017%;'.
sgr0: '\E[0;10m', '\E[m\017'.
smacs: '\E[11m', '^N'.
smam: NULL, '\E[?7h'.
smcup: NULL, '\E7\E[?47h'.
smkx: NULL, ''.
smpch: '\E[11m', NULL.
u6: '\E[%i%d;%dR', NULL.
u8: '\E[?6c', '\E[?1;2c'.
--
Thomas E. Dickey [EMAIL PROTECTED]
http://dickey.his.com
ftp://dickey.his.com
ssh and default bg color problem
I currently run mutt in two different situations: 1. on my home machine (linux) in a transparent Eterm window 2. ssh-ing into my home machine from a Windows box. When I'm home, I set all my background colors to "default" so that the transparent Eterm effect works in X. However, when I'm on a Windows box and I ssh into my machine, the "default" background color causes problems. The "current message" bar's colors bleed into the next item in the message index, and when viewing in the pager, the header colors bleed into my message text. To solve this issue, I set the background to "black" when I ssh into the box and everything color-wise is ok. This works because I don't need the transparent backgrounds when I ssh in. But now, based on where I am, I constantly have to rename my .mutt_colors file (which is "sourced" by my .muttrc) depending on whether I'm using ssh or whether I'm local, running under X. This is very frustrating. So who's at fault? Is it mutt for not using slang/ncurses correctly? Is it slang/ncurses not being able to handle the default color? Is it my ssh client not supporting the correct terminal type? -- Nathan Cullen [EMAIL PROTECTED]
Re: ssh and default bg color problem
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote: I currently run mutt in two different situations: 1. on my home machine (linux) in a transparent Eterm window 2. ssh-ing into my home machine from a Windows box. When I'm home, I set all my background colors to "default" so that the transparent Eterm effect works in X. However, when I'm on a Windows box ...what terminal emulator are you using? - that's the place to start. -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: ssh and default bg color problem
On Tue, Dec 26, 2000 at 11:29:28AM -0500, Nathan Cullen wrote: I currently run mutt in two different situations: 1. on my home machine (linux) in a transparent Eterm window Yay. 2. ssh-ing into my home machine from a Windows box. My condolences :-). When I'm home, I set all my background colors to "default" so that the transparent Eterm effect works in X. However, when I'm on a Windows box and I ssh into my machine, the "default" background color causes problems. The "current message" bar's colors bleed into the next item in the message index, and when viewing in the pager, the header colors bleed into my message text. To solve this issue, I set the background to "black" when I ssh into the box and everything color-wise is ok. This works because I don't need the transparent backgrounds when I ssh in. Here's a novel workaround, which may solve more than just your Mutt problem, and may or may not work based on with what you have to work. 1.) install VNC (X) (http://www.uk.research.att.com./vnc/) 2.) arrange for your display manager (e.g., xdm) to start Xvnc and to put up a login dialog on your VNC server (optional) 3.) install VNC (Win32, or WinVNC) 4.) ssh in using port forwarding, and possibly compression (VanDyke's SecureCRT is one such Win32 program that will do that) 5.) use WinVNC to connect to your local machine on the port being forwarded by your ssh client (e.g., mycomputer:1 to connect to a ssh listening on mycomputer's TCP port 5901). This (in a slightly more convoluted fashion due to a proxy also being in the way) is what I do to run my X apps "securely," including xterms running Mutt in them. I use VNC to take advantage of its graphical encoding/compression (over just using bare X11), and use ssh's compression on top of that. Over my present V.90 connection, it's not too bad. -- Oo---o, Oo---o, O-weem-oh-wum-ooo-ayyy In the jungle, the silicon jungle, the process sleeps tonight. Joe Philipps [EMAIL PROTECTED], http://www.philippsfamily.org/Joe/ public PGP/GPG key 0xFA029353 available via http://www.keyserver.net PGP signature
Re: color problem
On Mon, Nov 29, 1999 at 06:36:20PM -0600, David DeSimone wrote: : : set quote_regexp="^([ \t]?[ \t]?[:|])+" I'm curious, I don't quite understand the logic behind setting your quote matching to this kind of pattern instead of using the default: set quote_regexp="^([ \t]*[|#:}])+" -- Eugene Lee [EMAIL PROTECTED]
Re: color problem
George Georgalis [[EMAIL PROTECTED]] wrote: I'm having problems with quoted colorings. At one point I thought the mutt viewer would use a different color for each of the adjoining lines below color1 color2 color1 color2 They display in different colors in vim, but they are all the same in the viewer? Does the viewer have that capacity? I'm using mutt-1.0pre3i-1. The pager has that ability, and the lines show in different colors for me. Here are the relevant lines from my .muttrc: color quoted greendefault color quoted1 yellow default color quoted2 greendefault color quoted3 yellow default -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Re: color problem
George Georgalis [[EMAIL PROTECTED]] wrote: I'm having problems with quoted colorings. At one point I thought the mutt viewer would use a different color for each of the adjoining lines below color1 color2 color1 color2 They are all the same color for me, too. However, the following lines look different: color1 color2 color3 color4 It's not even consistent. Sometimes, the "color2" line will be shown in color1. Anything with multiple quotes () ends up in color1. I'm using mutt-1.0-pre-something. So, I don't know how it determines what colors to use. Sometimes it'll even change colors in mid-viewing, if I scroll the page. _ _ _ _ ___ ___ "Use the source, Luke!"- ( \/ ( \/ (__ (__ ) | Scott Scriven (Toy Keeper / XYZZ)| \ / \ / // // | mailto:[EMAIL PROTECTED] | / \ / / //_ //_ | irc:serdevian.dyn.omnipotent.net | (_/\_(_/ (___(___) | http://www.vis.colostate.edu/~scriven/ |
Re: color problem
Scott Scriven [[EMAIL PROTECTED]] wrote: George Georgalis [[EMAIL PROTECTED]] wrote: I'm having problems with quoted colorings. At one point I thought the mutt viewer would use a different color for each of the adjoining lines below color1 color2 color1 color2 They are all the same color for me, too. However, the following lines look different: color1 color2 color3 color4 It's not even consistent. Sometimes, the "color2" line will be shown in color1. Anything with multiple quotes () ends up in color1. I'm using mutt-1.0-pre-something. Well, I'm guessing the value of $quote_regexp comes into play here, but see below. So, I don't know how it determines what colors to use. Sometimes it'll even change colors in mid-viewing, if I scroll the page. This really sounds like an issue of your $TERM or term library... I'd try other options and see if you can figure it out (other terminal emulators, etc.). -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Re: color problem
George Georgalis [EMAIL PROTECTED] wrote: color1 color2 color1 color2 They display in different colors in vim, but they are all the same in the viewer? For me, they show up in different colors. You need two things to make this work: 1. Some colors defined for multiple quote levels 2. A proper quote_regexp that will match repeated quote levels properly Here's my settings for (1): color quoted green black color quoted1white black color quoted2brightred black color quoted3magenta black color quoted4red black And here's my setting for (2): set quote_regexp="^([ \t]?[ \t]?[:|])+" Mutt will notice and colore more than five levels of quoting; it will simply re-use the colors again, if I remember rightly. The quote_regexp format is very important. It must match *only* the text at the front of the line, that forms the "quote" section. If it ends up matching the entire line, then all quotes will appear at the same "level." The reason for this is that Mutt looks at the *length* of the string that matches the regular expression. Each time a new length is seen, it is treated as a new level of quoting. Note, longer lengths are not treated as deeper levels, just *different* levels. Have fun. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
