color
I just did a very minimal installation of redhat 6.1 and I have lost my colors... something to the extent of color command not found when parsing my configs Mutt 1.1.11i (2000-03-30) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.2.12-20 [using ncurses 4.2] Compile options: -DOMAIN -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX -HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS -COMPRESSED SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/usr/local/lib/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the muttbug utility. What is the package I need to load to get color into the console or xterms?
color
I'm trying to set up color with mutt (1.2.5i) but I am getting "color: unknown command" errors from my muttrc. Is there some trick that I'm missing? Mike -- Mike Erickson http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Color
I noticed say in an Eterm or Xterm, the color green, is more like a neon or Matrix like green, whereas in mutt, it is more like a dull green. Could someone explain this to me..? -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Color
I understand how to use the color settings in the configuration file. My problem is that although I use color_xterm which is fully color compatible (including using color0 etc) I can't figure out how I convince mutt to use color. At first I thought I was doing something wrong, but when I added in some 'mono' configuration options these immediately began working. I don't see anything in the manual or man pages related to forcing mutt to use the color options rather than the mono ones. I've tried switching my TERM from xterm to vt100 just out of curiosity, but of course that didn't do anything. What's up? How can I get this going? Dave
color
please can sombody tell me how to enable colors in mutt i have a color xterm and vim has colors in it what must i do for mutt ot work here also TIA JJK _ /| John J Kearney |\ | Wireless(Bluetooth)Group| ///| Powering The Mobile Internet |\\\ <<<<<<<<<| Parthus Technologies Plc |>>>>>>>>> \\\| 32-34 Harcourt st.,D2, IRELAND |/// | mailto:[EMAIL PROTECTED] | \|___|/
Re: color definitions using the "current" color
* Stephane ENTEN ([EMAIL PROTECTED]) [990820 16:31]: > > Mutt's "color header" colorizes complete lines only. :-/ > About that, I'd like to know if someone has a > way to colorize the whole line with a background. That reminds me: Coloring addresses in quoted text do have the background color of the quoted text - even when you define "default" as the background color. I suppose the "default" simply refers to default color of the *terminal*. I think we need a description that can make use of the "current color". Here's an example of what I'd like to use: color quoted white blue color body green current "(ftp|http):[^ ]*" And what I'd like to see: > quoted text with a URL http://www.guckes.net within _*___ Now,the text above the underscores is displayed in "white on blue" whereas the text above the asterisks is displayed in "green on blue". Sounds like a simple patch... anyone? Sven
Mutt & Color
Hello I want to add color support to MUTT I used some of the sample configuration files on the mutt.org website but any of the ones i use all give erors regarding the color lines the error it gives is: Error in /home/jerry/.muttrc, line 29: color: unknown command Error in /home/jerry/.muttrc, line 30: color: unknown command Error in /home/jerry/.muttrc, line 31: color: unknown command Error in /home/jerry/.muttrc, line 32: color: unknown command Error in /home/jerry/.muttrc, line 33: color: unknown command Error in /home/jerry/.muttrc, line 42: color: unknown command etc. etc. I'm running FreeBSD 3.5-STABLE and installed mutt directly from the ports with a simple `make install` however i have *no* trace of anything relating to X11 on my system could this be why i cannot have color support in mutt? if so how can i get around it? Any help would be greatly appreciated, Thanks in advance, Jerry.
Re: color
On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: > I'm trying to set up color with mutt (1.2.5i) but I am getting > "color: unknown command" errors from my muttrc. Is there some trick > that I'm missing? > Perhaps you should try colour instead :) Seriously, can you post a few lines before and after the color statement?
Re: color
On Fri, Oct 20, 2000 at 10:50:03PM +0800, Anthony Liu wrote:
> On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote:
> > I'm trying to set up color with mutt (1.2.5i) but I am getting
> > "color: unknown command" errors from my muttrc. Is there some trick
> > that I'm missing?
> >
> Perhaps you should try colour instead :)
>
> Seriously, can you post a few lines before and after the color
> statement?
Here ya go: (`r!cat ~/.muttrc | grep -5 color` -- gotta love vi)
# set index format string
set index_format="%4C %Z %{%b %d} %-15.15F (%4l) %s"
# COLOR
color quoted brightblue default
color signature red green
color indicator green black
color error brightred default
color status yellow blue
color tree magenta default
color tilde magenta default
color message brightcyan default
color markers brightcyan brightblue # Should be default for val 2
color attachment brightmagenta default
color search default green
color header brightred default ^(From|Subject):
color body magenta default "(ftp|http)://[^ ]+" # point out URLs
color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+# e-mail addresses
color underline brightgreen default
# KEY BINDINGS
bind index j next-entry
bind index k previous-entry
bind pager j next-entry
Mike
--
Mike Erickson http://www.quidquam.com/
"Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
On 20 Oct 2000, at 22:50, Anthony Liu wrote: > On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: > > I'm trying to set up color with mutt (1.2.5i) but I am getting > > "color: unknown command" errors from my muttrc. Is there some trick > > that I'm missing? > > > Perhaps you should try colour instead :) > > Seriously, can you post a few lines before and after the color > statement? Hi, Actually, it sounds like color support has been turned off. What does the output from "mutt -v" show. Specifically, what curses lib is your mutt built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? -Harold -- "Life sucks, deal with it!"
Re: color
On Fri, Oct 20, 2000 at 10:29:17AM -0600, Harold Oga wrote: > On 20 Oct 2000, at 22:50, Anthony Liu wrote: > > On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: > > > I'm trying to set up color with mutt (1.2.5i) but I am getting > > > "color: unknown command" errors from my muttrc. Is there some trick > > > that I'm missing? > > > > > Perhaps you should try colour instead :) > > > > Seriously, can you post a few lines before and after the color > > statement? > Hi, >Actually, it sounds like color support has been turned off. What does > the output from "mutt -v" show. Specifically, what curses lib is your mutt > built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? Sure enough -HAVE_COLOR is in the compile options. However, when I went back to the source and did a ./configure --help, I didn't see any option to include color support. How do I recompile with color support? Thanks Mike -- Mike Erickson http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
Sounds like your curses lib doesn't support color. You might try ncurses * Mike E <[EMAIL PROTECTED]> [001020 11:56]: > On Fri, Oct 20, 2000 at 10:29:17AM -0600, Harold Oga wrote: > > On 20 Oct 2000, at 22:50, Anthony Liu wrote: > > > On Fri, Oct 20, 2000 at 02:56:30AM -0700, Mike E wrote: > > > > I'm trying to set up color with mutt (1.2.5i) but I am getting > > > > "color: unknown command" errors from my muttrc. Is there some trick > > > > that I'm missing? > > > > > > > Perhaps you should try colour instead :) > > > > > > Seriously, can you post a few lines before and after the color > > > statement? > > Hi, > >Actually, it sounds like color support has been turned off. What does > > the output from "mutt -v" show. Specifically, what curses lib is your mutt > > built against and does "mutt -v" show +HAVE_COLOR or -HAVE_COLOR? > > Sure enough -HAVE_COLOR is in the compile options. However, when I went > back to the source and did a ./configure --help, I didn't see any option > to include color support. How do I recompile with color support? > > Thanks > Mike > > -- > Mike Erickson http://www.quidquam.com/ > "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Re: color
On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: > Sounds like your curses lib doesn't support color. You might try > ncurses here is the full output of mutt -v Mutt 1.2.5i (2000-07-28) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX -HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the muttbug utility. Mike -- Mike Erickson http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: color
* Mike E <[EMAIL PROTECTED]> [001020 12:14]: > On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: > > Sounds like your curses lib doesn't support color. You might try > > ncurses As I said, the curses lib doesn't support color... Here is my mutt -v: Mutt 1.3.10i (2000-10-11) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: UnixWare 5 Compile options: DOMAIN="lerctr.org" +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_GSS +USE_SSL +USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV +ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL="/usr/local/bin/ispell" SENDMAIL="/etc/mail/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the flea(1) utility. > > here is the full output of mutt -v > > > Mutt 1.2.5i (2000-07-28) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] > Compile options: > -DOMAIN > -DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK > -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX > -HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > SHAREDIR="/usr/local/share/mutt" > SYSCONFDIR="/usr/local/etc" > -ISPELL > To contact the developers, please mail to <[EMAIL PROTECTED]>. > To report a bug, please use the muttbug utility. > > Mike > > -- > Mike Erickson http://www.quidquam.com/ > "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
Re: color
On Fri, Oct 20, 2000 at 10:02:31AM -0700, Mike E wrote: > System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] You'd better obtain more recent version of ncurses and recompile. I have version 4.2 while you have only 1.8.6. -- Eugene Paskevich | *==(--- | "Alrighty then!" [EMAIL PROTECTED]| ---)==* |-- Ace Venture Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey Fingerprint: 03 BE 52 C8 41 8C 10 DC 2F 81 A2 21 28 5E D3 12 ## A friend in need is a pest indeed. ##
Re: color
On Fri, 20 Oct 2000, Mike E wrote: > On Fri, Oct 20, 2000 at 12:01:13PM -0500, Larry Rosenman wrote: > > Sounds like your curses lib doesn't support color. You might try > > ncurses > > here is the full output of mutt -v that version "does", but mutt's configure script does not recognize it. > Mutt 1.2.5i (2000-07-28) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] -- T.E.Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: color
On Fri, Oct 20, 2000 at 08:43:13PM +0300, Eugene Paskevich wrote: > On Fri, Oct 20, 2000 at 10:02:31AM -0700, Mike E wrote: > > System: FreeBSD 3.4-STABLE [using ncurses 1.8.6/ache] > You'd better obtain more recent version of ncurses and recompile. > I have version 4.2 while you have only 1.8.6. The current version of ncurses is 5.1 (2708) There's an faq at http://dickey.his.com/ncurses/ncurses.faq.html -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
more color
Okay, previously I had a problem with color, and it was resolved that I was using a version of ncurses that was too old. On another server (OpenBSD 2.7) I've compiled mutt to test it out. Here is my mutt -v output: ~ $ mutt -v Mutt 1.2.4i (2000-07-07) Copyright (C) 1996-2000 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: OpenBSD 2.7 [using ncurses 5.0] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" SHAREDIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" -ISPELL To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the muttbug utility. I have +HAVE_COLROR and ncurses 5.0. However color still isn't working. I get no .muttrc errors on my color commands when running mutt, and color works in other programs (like BitchX), so I'm pretty stumped. Anyone have any ideas? Mike -- Mike Erickson http://www.quidquam.com/ "Hatred is the coward's revenge for being intimidated" - George Bernard Shaw
Re: Color
On Wed, Oct 25, 2000 at 09:31:06PM -0700, Jason Helfman wrote: > I noticed say in an Eterm or Xterm, the color green, is more like a neon > or Matrix like green, whereas in mutt, it is more like a dull green. > > Could someone explain this to me..? That's just the particular X resource chosen by the person who implemented, packaged or installed that terminal. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Attachments + color
Hi, I have a little problem with mutt colors. For some reason my attachements are shown in black on black and I cannot figure out which color parameter dictates that. This is the list I get when I press 'v' to view attachements I'm talking about. Thanks in advance. //Fredde
color quotes
I've found another (I think, well-known) `funny feature'. When not all level of quotes fits the first screen and they start from `the oldest', mutt's changing colors of next (`newer') ones when they appear. I'm not sure if I describe it well, try: > > > > > > > quote1 [... 7 times ...] > > > > > > quote2 [... 7 times ...] > > > > > quote3 [... 7 times ...] > > > > quote4 [... 7 times ...] > > > quote5 [... 7 times ...] Shouldn't mutt search whole message for `>', next for `> >', next `> > >' and so on and after that color quotes depending gathered information? It could slow down viewing each letter, but ``every good thing comes with a price'' ;-). Maybe this price's not so high? -- Daniel `bonkey' Bauke -=- http://www.ogurek.pi.pl/~bonkey/ -=- +48604879529 --- Politics: A strife of interests masquerading as a contest of principles. The conduct of public affairs for private advantage. -- Ambrose Bierce
subject color
Hello: I was wondering if it's possible to color the title of an email message like: 1 b Mar 18 To LUG ( 13) [WLUG] nslookup ^^^ | different color Thanks -- -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*- | Ayman Haidar| | [EMAIL PROTECTED] | | just another linux and vi lover.| -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
tag color
How could set the color of the tagged messages ? I could find out the way to do that. Thx in advance
Color Issues
Hello, I've been using Mutt for a few weeks now and I like it. However, one of the reasons I did start using it was so I could have a color mail client for Linux. I connect to my Linux box using SecureCRT (an ssh client for Win95) and if I set up as VT100 with "ANSI Color" on, I can see color objects such as Linux's directory colors. But Mutt doesn't work. I tried creating the term files like it says in the FAQ but it's obvious they're made for an xterm window and not a terminal emulator. However, I'd like to think that if Linux itself can do color, so can Mutt. I'd appreciate any help anybody could give, having a black-and-white e-mail program is such a drag :-). Mark
color question
Hi- I wrote a mail agent front end that layered something a lot like Emac's dired utility on top of mh. I'd still be using it but my inbox is about 3000 messages and using mh is just too slow. So I'm switching to mutt, mutt looks cool. However, one feature that I had that I really miss is this: I could have a list of addresses and have color highlighting in the index based on those addresses. Mutt has support for mailing lists, but that - while useful - isn't what I want. A simple version of what I want is that all messages sent to "lm@*" or CC-ed to are highlighted with a color on the index page. Is there a way to do this? And is there a way to have an arbitrary list of those? It's really useful. I get between 300-1000 messages a day and I really want to be able to pick through and get the stuff that is to me highlighted. I have this bad habit of cleaning out my mailbox early in the morning before coffee. You can imagine the need for the highlighting... Thanks in advance. --lm
Color xterm??
Is color xterm a requirement for mutt's color feature? I am using Slackware 4. The "ls" command has several color options, where I see a different color for each file type. If this xterm works for "ls" with color, then mutt's got to work too. I have installed ncurses-5.0 and that is not helping either. Any pointers to get colors working... Subba Rao [EMAIL PROTECTED] http://pws.prserv.net/truemax/
color problem
Hi all, I hope this isn't an old conversation, but... 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. Please reply directly as I'm not on this list, I will provide my .muttrc for anyone who wants to see it, and I'm attaching my mutt wrapper for those who would like to try it, it launches fetchmail -d while mutt is running and allows only the first instance of mutt to be read-write. TIA, // George -- +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ GEORGE GEORGALISICXC 858.621.9488 [EMAIL PROTECTED]NIKI PO Box 3342 http://galis.org La Jolla, CA 92038 +=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
color headers
I've been using mutt for some weeks now. Originally, I found the colors to be most helpful in some cases and a distraction in others. Early on I made some changes to suit my own old eyesight and left the headers for later. Now I've decided the only headers I need to see are 'from', 'date', 'reply-to' and 'subject' - with 'subject' made to stand out and so be easy to see. In .muttrc, I used:- -- ignore * unignore date from reply-to subject -- and also :- -- color header blue default ^Subject color header black green ^From etc -- This gave me what I desired, plus, something I do not need, a 'ghost' line in the form of (for this list) - 'From mutt-users-owner-' . When I say 'ghost' line, it looks something like the old typewriter correction fluid in action - you can just read what's underneath. I still have kmail on this box, and when I bring up the 'full headers' for sample messages there is no 'From' in exactly the same form. I notice in /etc/Muttrc amongst the weeding of header fields, there is:- ignore "from" received message-id etc etc Can anyone please explain to me what is happening and what I can best do to get rid of the 'ghost' ( I was patting myself on the back with the way messages are now displayed for reading etc until I noticed this, and now it's the first thing my eyes alight on!!) Thanks, John.
Re: Color
On Thu, Sep 6, 2001, Dave Spracklen wrote: > I understand how to use the color settings in the configuration file. My > problem is that although I use color_xterm which is fully color compatible > (including using color0 etc) I can't figure out how I convince mutt to use > color. At first I thought I was doing something wrong, but when I added in some > 'mono' configuration options these immediately began working. I don't see > anything in the manual or man pages related to forcing mutt to use the color > options rather than the mono ones. I've tried switching my TERM from xterm to > vt100 just out of curiosity, but of course that didn't do anything. What's up? > How can I get this going? I don't know what OS you are on, but under Solaris, the only term that would work to get color was dtterm. I figured this out since color would work in the CDE Terminal, but not under any other, with whatever other term settings I tried. HTH... -Ken
Re: Color
this is actually a reply to the original message which I (unfortunately)
deleted.
try TERM=xterm-color
I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt
would pop up, but be in mono. So my wrapper is as follows
#!/bin/bash
wait 1;
export TERM=xterm-color;
/usr/bin/mutt;
seems to work...
tw
Le jour Thu Sep 06, 2001 at 11:36:49AM -0400, Ken Weingold ([EMAIL PROTECTED]) a
écrit...
> On Thu, Sep 6, 2001, Dave Spracklen wrote:
> > I understand how to use the color settings in the configuration file. My
> > problem is that although I use color_xterm which is fully color compatible
> > (including using color0 etc) I can't figure out how I convince mutt to use
> > color. At first I thought I was doing something wrong, but when I added in some
> > 'mono' configuration options these immediately began working. I don't see
> > anything in the manual or man pages related to forcing mutt to use the color
> > options rather than the mono ones. I've tried switching my TERM from xterm to
> > vt100 just out of curiosity, but of course that didn't do anything. What's up?
> > How can I get this going?
>
> I don't know what OS you are on, but under Solaris, the only term that
> would work to get color was dtterm. I figured this out since color
> would work in the CDE Terminal, but not under any other, with whatever
> other term settings I tried.
>
> HTH...
>
>
> -Ken
--
Timothy Mark Whitehead // Sophomore, UW - Madison
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!!
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net // Do you, eh, look at headers?
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }
Re: Color
* Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 09:05 -0700]: > >this is actually a reply to the original message which I (unfortunately) >deleted. > >try TERM=xterm-color > >I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt >would pop up, but be in mono. So my wrapper is as follows > >#!/bin/bash > >wait 1; >export TERM=xterm-color; >/usr/bin/mutt; it almost sounds like this could be set in the .bashrc, .tcshrc, or whatever the shell that you are using, no? i've never used gkrellm, but does it not set TERM variable at all? if it does, then you can put it a small condition to reset it to something more appropriate in your startup file. just a suggestion, denis -- // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]> // icq : 12359698 // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
Re: Color
I think that the problem is in my /etc/profile
if [ "$COLORTERM" = "Eterm" ]; then
TERM=xterm-color
else
TERM=linux
fi
This may be what is throwing off the TERM var. Because when I comment out the
wait line, mutt comes up in mono again.
any suggestions?
tw
Le jour Thu Sep 06, 2001 at 09:59:48AM -0700, Denis Perelyubskiy ([EMAIL PROTECTED])
a écrit...
> * Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 09:05 -0700]:
> >
> >this is actually a reply to the original message which I (unfortunately)
> >deleted.
> >
> >try TERM=xterm-color
> >
> >I just had to write a wrapper so I could have gkrellm call mutt. Originally mutt
> >would pop up, but be in mono. So my wrapper is as follows
> >
> >#!/bin/bash
> >
> >wait 1;
> >export TERM=xterm-color;
> >/usr/bin/mutt;
>
> it almost sounds like this could be set in the .bashrc,
> .tcshrc, or whatever the shell that you are using, no?
>
> i've never used gkrellm, but does it not set TERM variable
> at all? if it does, then you can put it a small condition to
> reset it to something more appropriate in your startup file.
>
> just a suggestion,
>
> denis
>
> --
> // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]>
> // icq : 12359698
> // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
--
Timothy Mark Whitehead // Sophomore, UW - Madison
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!!
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net // Do you, eh, look at headers?
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }
Re: Color
* Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 10:18 -0700]: > >I think that the problem is in my /etc/profile > >if [ "$COLORTERM" = "Eterm" ]; then >TERM=xterm-color >else >TERM=linux >fi > >This may be what is throwing off the TERM var. Because >when I comment out the wait line, mutt comes up in mono >again. > >any suggestions? maybe something along the lines of if [ "$COLORTERM" = "Eterm" ]; then TERM=xterm-color elif [ "$TERM" = "gkrellm" ]; then TERM=xterm-color else TERM=linux fi i am not too good with bash in general. i just go try to figure out things i need wheni need them :) also, check what $TERM var says when you log in using your gkrellm. that test in 'elif' may need to be modified if TERM is not gkrellm also, neither do i know if this is an *official* bash way, but things like these work in my startup files, even though maybe they disgust people who really know bash :) denis -- // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]> // icq : 12359698 // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
Re: Color
Denis Perelyubskiy wrote: > maybe something along the lines of > > if [ "$COLORTERM" = "Eterm" ]; then > TERM=xterm-color > elif [ "$TERM" = "gkrellm" ]; then > TERM=xterm-color > else > TERM=linux > fi i only use xterm-color when i have to - apparently it's a bad setting to use for some reason (maybe someone else can clarify this). if you're using XFree86, xterm-xfree86 might be a better setting if it works. w -- Sintax error in config file! (line 378) aborted! PGP Public Key: http://infinitejazz.net/will/pgp/
Re: Color
On Thu, Sep 06, 2001 at 02:05:34PM -0700, Will Yardley wrote: > Denis Perelyubskiy wrote: > > maybe something along the lines of > > > > if [ "$COLORTERM" = "Eterm" ]; then > > TERM=xterm-color > > elif [ "$TERM" = "gkrellm" ]; then > > TERM=xterm-color > > else > > TERM=linux > > fi > > i only use xterm-color when i have to - apparently it's a bad setting to > use for some reason (maybe someone else can clarify this). if you're > using XFree86, xterm-xfree86 might be a better setting if it works. ditto for Eterm (it comes with its own terminfo entry, which also is in ncurses). -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: Color
On 2001.09.06, in <[EMAIL PROTECTED]>, "Denis Perelyubskiy" <[EMAIL PROTECTED]> wrote: > > also, neither do i know if this is an *official* bash way, > but things like these work in my startup files, even though > maybe they disgust people who really know bash :) What bothers me about this approach, in general, is that it's not supposed to depend on your shell -- you're not supposed to need to make tests and reset $TERM accordingly at all. The point of terminfo/termcap and the $TERM variable is that the terminal emulator application should tell the shell what terminal it's emulating by means of $TERM, and everything should work. If it doesn't, then something is wrong with your terminfo library or your termcap file, or your terminal emulator is lying. needs new options or resources. That said, I occasionally change my $TERM from xterm to something I like, just to get rid of the alternate (application-mode?) screen setting. But there are better ways of doing this (xterm -ti vt100, or modifying a private copy in $TERMINFO); I'm just lazy. I suspect that there's always a better approach than shell-rc case switching. If not, then your terminal emulator needs new options or resources. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Color
* David Champion <[EMAIL PROTECTED]> [09-Thu-01 14:59 -0700]: > >What bothers me about this approach, in general, is that it's not >supposed to depend on your shell -- you're not supposed to need to make >tests and reset $TERM accordingly at all. The point of terminfo/termcap >and the $TERM variable is that the terminal emulator application should >tell the shell what terminal it's emulating by means of $TERM, and >everything should work. this makes sense to me >If it doesn't, then something is wrong with your terminfo library or >your termcap file, or your terminal emulator is lying. >needs new options or resources. perhaps. i do this in particular for "cygwin" terminal type, since that's the type you get if you try to ssh (using ssh that comes with cygwin) from win2k shell prompt. denis -- // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]> // icq : 12359698 // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
Re: Color
On Thu, Sep 06, 2001 at 04:56:58PM -0500, David Champion wrote: > That said, I occasionally change my $TERM from xterm to something I > like, just to get rid of the alternate (application-mode?) screen > setting. But there are better ways of doing this (xterm -ti vt100, or > modifying a private copy in $TERMINFO); I'm just lazy. or better yet, it's a popup entry in XFree86 xterm. I set my $TERM manually for one of these reasons: a) the actual $TERM isn't propagated to the shell from where I'm logged in. b) to work around broken applications/libraries that can't handle the terminfo. c) testing... -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: Color
On 2001.09.06, in <[EMAIL PROTECTED]>, "Thomas Dickey" <[EMAIL PROTECTED]> wrote: > > or better yet, it's a popup entry in XFree86 xterm. I don't use XFree86. I think that its xterm was the same as the one on your web site, though, which I do use (on Solaris). I see the "Show Alternate Screen" item, but that seems just to toggle whether I currently see the alternate screen. My problem is that with TERM=xterm, applications will use the alternate screen, then flip back when they suspend or terminate. I don't like that - I want applications and shell in the standard screen, with no automatic toggling of the alternate screen. Is there a way to force that without editing the terminfo or changing $TERM? > I set my $TERM manually for one of these reasons: > > a) the actual $TERM isn't propagated to the shell from where I'm > logged in. Isn't that (arguably) a flaw in your communications application or protocol? I thought that all the standard daemons supported this -- well, as of about 1991, anyway. I don't recall exactly when it showed up in telnetd. > b) to work around broken applications/libraries that can't handle > the terminfo. > > c) testing... Which make sense, of course, but are more of a one-off event than something to keep in your .profile. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Color
On Thu, Sep 06, 2001 at 06:07:20PM -0500, David Champion wrote: > I see the "Show Alternate Screen" item, but that seems just to toggle > whether I currently see the alternate screen. My problem is that with > TERM=xterm, applications will use the alternate screen, then flip back > when they suspend or terminate. I don't like that - I want applications > and shell in the standard screen, with no automatic toggling of the > alternate screen. Is there a way to force that without editing the > terminfo or changing $TERM? There's also "Enable Alternate Screen Switching". Just glancing at the changelog, it appears I added that around patch #90. > > I set my $TERM manually for one of these reasons: > > > > a) the actual $TERM isn't propagated to the shell from where I'm > >logged in. > > Isn't that (arguably) a flaw in your communications application or > protocol? I thought that all the standard daemons supported this -- > well, as of about 1991, anyway. I don't recall exactly when it showed up > in telnetd. sure - but in the cases where it breaks, it's usually on someone else's network (I can't fix those ;-) > > > b) to work around broken applications/libraries that can't handle > >the terminfo. > > > > c) testing... > > Which make sense, of course, but are more of a one-off event than > something to keep in your .profile. > > -- > -D. [EMAIL PROTECTED]NSITUniversity of Chicago -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: Color
I think you're confused as to what gkrellm is. The website is www.gkrellm.net
Essentially it's a system monitor that has the capability to check mail (as well
as a few other things), either locally or remotely. In my case I have it call
'fetchmail' every 10 minutes. It checks my local mailbox every 5 seconds for new
mail. When there's mail I have the option of calling a mail reader. So I pop up
an Eterm and run mutt.
Thus, there would not be a TERM=gkrellm; it doesn't make sense.
tw
Le jour Thu Sep 06, 2001 at 01:55:34PM -0700, Denis Perelyubskiy ([EMAIL PROTECTED])
a écrit...
> * Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 10:18 -0700]:
> >
> >I think that the problem is in my /etc/profile
> >
> >if [ "$COLORTERM" = "Eterm" ]; then
> >TERM=xterm-color
> >else
> >TERM=linux
> >fi
> >
> >This may be what is throwing off the TERM var. Because
> >when I comment out the wait line, mutt comes up in mono
> >again.
> >
> >any suggestions?
>
> maybe something along the lines of
>
> if [ "$COLORTERM" = "Eterm" ]; then
> TERM=xterm-color
> elif [ "$TERM" = "gkrellm" ]; then
> TERM=xterm-color
> else
> TERM=linux
> fi
>
> i am not too good with bash in general. i just go try to
> figure out things i need wheni need them :)
>
> also, check what $TERM var says when you log in using your
> gkrellm. that test in 'elif' may need to be modified if TERM
> is not gkrellm
>
> also, neither do i know if this is an *official* bash way,
> but things like these work in my startup files, even though
> maybe they disgust people who really know bash :)
>
> denis
>
> --
> // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]>
> // icq : 12359698
> // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
--
Timothy Mark Whitehead // Sophomore, UW - Madison
tmwhitehead(at)students.wisc.edu// Intended Major: Computer Engineering
tigmoid(at)146.151.75.25// SUPPORT YOUR LOCAL COLLEGE STUDENT!!
whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
tigmoid(at)jps.net // Do you, eh, look at headers?
public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }
Re: Color
ok, my mistake. i thought it was a type of an xterm. clearly
that was wrong :)
denis
* Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 16:47 -0700]:
>
>I think you're confused as to what gkrellm is. The website is www.gkrellm.net
>
>Essentially it's a system monitor that has the capability to check mail (as well
>as a few other things), either locally or remotely. In my case I have it call
>'fetchmail' every 10 minutes. It checks my local mailbox every 5 seconds for new
>mail. When there's mail I have the option of calling a mail reader. So I pop up
>an Eterm and run mutt.
>
>Thus, there would not be a TERM=gkrellm; it doesn't make sense.
>
>
>tw
>
>
>Le jour Thu Sep 06, 2001 at 01:55:34PM -0700, Denis Perelyubskiy ([EMAIL PROTECTED])
>a écrit...
>
>> * Tim Whitehead <[EMAIL PROTECTED]> [09-Thu-01 10:18 -0700]:
>> >
>> >I think that the problem is in my /etc/profile
>> >
>> >if [ "$COLORTERM" = "Eterm" ]; then
>> >TERM=xterm-color
>> >else
>> >TERM=linux
>> >fi
>> >
>> >This may be what is throwing off the TERM var. Because
>> >when I comment out the wait line, mutt comes up in mono
>> >again.
>> >
>> >any suggestions?
>>
>> maybe something along the lines of
>>
>> if [ "$COLORTERM" = "Eterm" ]; then
>> TERM=xterm-color
>> elif [ "$TERM" = "gkrellm" ]; then
>> TERM=xterm-color
>> else
>> TERM=linux
>> fi
>>
>> i am not too good with bash in general. i just go try to
>> figure out things i need wheni need them :)
>>
>> also, check what $TERM var says when you log in using your
>> gkrellm. that test in 'elif' may need to be modified if TERM
>> is not gkrellm
>>
>> also, neither do i know if this is an *official* bash way,
>> but things like these work in my startup files, even though
>> maybe they disgust people who really know bash :)
>>
>> denis
>>
>> --
>> // mailto: Denis Perelyubskiy <[EMAIL PROTECTED]>
>> // icq : 12359698
>> // PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
>
>--
>Timothy Mark Whitehead// Sophomore, UW - Madison
>tmwhitehead(at)students.wisc.edu // Intended Major: Computer Engineering
>tigmoid(at)146.151.75.25 // SUPPORT YOUR LOCAL COLLEGE STUDENT!!
>whitehea(at)cs.wisc.edu // -- UW-Navs, UW-Band, UW-Trumpet
>tigmoid(at)jps.net// Do you, eh, look at headers?
>public static String sig(String sig) { if(sig.equals(this.sig))sig = sig(sig); }
denis
--
// mailto: Denis Perelyubskiy <[EMAIL PROTECTED]>
// icq : 12359698
// PGP : http://www.cs.ucla.edu/~denisp/files/pgp.asc
Re: Color
On 2001.09.06, in <[EMAIL PROTECTED]>, "Thomas Dickey" <[EMAIL PROTECTED]> wrote: > > There's also "Enable Alternate Screen Switching". Just glancing at the > changelog, it appears I added that around patch #90. Hmm, I'm using patch 150, but I don't see that in my menu. I did find the titeInhibit resource, though: good enough for me. > sure - but in the cases where it breaks, it's usually on someone else's network > (I can't fix those ;-) OK, fair enough. I get a warped viewpoint from owning all the systems I have user rights on. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Color
On Thu, Sep 06, 2001 at 07:09:38PM -0500, David Champion wrote: > On 2001.09.06, in <[EMAIL PROTECTED]>, > "Thomas Dickey" <[EMAIL PROTECTED]> wrote: > > > > There's also "Enable Alternate Screen Switching". Just glancing at the > > changelog, it appears I added that around patch #90. > > Hmm, I'm using patch 150, but I don't see that in my menu. I did find > the titeInhibit resource, though: good enough for me. This is what I have in XTerm.ad - *vtMenu*titeInhibit*Label: Enable Alternate Screen Switching *vtMenu*activeicon*Label: Enable Active Icon *vtMenu*softreset*Label: Do Soft Reset *vtMenu*hardreset*Label: Do Full Reset *vtMenu*clearsavedlines*Label: Reset and Clear Saved Lines *vtMenu*tekshow*Label: Show Tek Window *vtMenu*tekmode*Label: Switch to Tek Mode *vtMenu*vthide*Label: Hide VT Window *vtMenu*altscreen*Label: Show Alternate Screen -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
lost color
Hi, I just installed mutt-devel 1.3.22i (coming from 1.2.5i) and lost the color display (everything is now B&W) My .muttrc is the same as before, my term is also unchanged (xterm). I tried also to set TERM to some other values (xterm-color, linux) to no avail. Is this a FAQ? Or is it a problem on my config? Thanks in advance, Fernan %mutt -v Mutt 1.3.22.1i (2001-08-30) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 4.3-RELEASE-p15 [using ncurses 5.1] Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -HAVE_WC_FUNCS -HAVE_LANGINFO_CODESET +-HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL="/usr/local/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER -- | F e r n a n A g u e r o | B i o i n f o r m a t i c s | | [EMAIL PROTECTED] | genoma.unsam.edu.ar |
Re: color
* John J Kearney ([EMAIL PROTECTED]) babbled: > please can sombody tell me how to enable colors in mutt here's what i use. ## = ## Color definitions ## ===== color attachment white magenta color body cyan default "ftp://[^ ]*" color body brightgreen default "[[:alnum:]][-+.#_[:alnum:]]*@[-+.[:alnum:]]*[[:alnum:]]" color body cyan default "" color bold green default color error reddefault color headeryellow default "^cc:" color headergreen default "^date:" color headeryellow default "^from" color headerbrightcyan default "^from:" color headeryellow default "^newsgroups:" color header yellow default "^reply-to:" color headerbrightcyan default "^subject:" color headergreen default "^to:" color headeryellow default "^x-mailer:" color headeryellow default "^message-id:" color headeryellow default "^Organization:" color header yellow default "^Organisation:" color headeryellow default "^User-Agent:" color headeryellow default "^message-id: .*pine" color indicator white blue color markers reddefault color message white blue ## == ## Colorizing the body of messages (ie in the pager) ## == color normalwhite default # pager body # Coloring quoted text - coloring the first 6 levels: color quotedcyan default color quoted1 yellowdefault color quoted2 red default color quoted3 green default color quoted4 cyan default color quoted5 yellowdefault color quoted6 red default color quoted7 green default color signature brightred default color statuswhite blue color tilde blue default color tree brightmagenta default color underline yellow default color body yellow default "[;:]-[)/(|]" # colorise smileys color body yellow default "[;:][)/(|]" color body brightblue default "(http|ftp|news|telnet|finger)://[^ ]*" color index yellow default ~N # New color index yellow default ~O # Old color index brightgreendefault '~s tgil' color index brightgreen default '~p'# mail to myself color index brightcyandefault '~P'# mail from myself color index magentadefault ~F # Flagged color index blue default ~T # Tagged color index reddefault ~D # Deleted -- ) ,_),_) (-(__ |_ _ _ |/ ) | |(_)(_ |\ ( \_, ___ | http://www.exitwound.org : hard to find | ___ | Five is a sufficiently close approximation| | to infinity. -- Robert Firth "One, two, | | five." -- Monty Python and the Holy Grail | ___ -BEGIN GEEK CODE BLOCK- | Version: 3.1 | | GJ/IT d- s: a C+++>$ UL P+++ L+++ E--- W++| | N+@ o K- w O- M- V PS+ PE Y+ PGP++ t+@ 5@ X++ | | R tv+@ b+ DI D+ G++ e h r+++ y+++ | --END GEEK CODE BLOCK--
Re: color
When I was first messing around with Mutt I had similar troubles when trying to use a regular old xterm. It seems like I found that setting the environment variable TERM to color_xterm instead of just xterm made it work. Calling xterm with the -tn color_xterm flag has a similar effect, I think. HTH --Daniel On Wed, Oct 31, 2001 at 06:02:17PM +, John J Kearney wrote: > please can sombody tell me how to enable colors in mutt > > i have a color xterm and vim has colors in it > > what must i do for mutt ot work here also > > TIA JJK
Re: color
* John J Kearney <[EMAIL PROTECTED]> [31-10-2001 19:01]: | please can sombody tell me how to enable colors in mutt | | i have a color xterm and vim has colors in it | | what must i do for mutt ot work here also Configure them in your .muttrc ;) See the 'color' section in `man muttrc`. -- René Clerc - ([EMAIL PROTECTED]) The creative is the place where no one else have ever been. You have to leave the city of your comfort and go into the wilderness of your intuition. -Alan Alda PGP signature
Re: color
Moin, * John J Kearney <[EMAIL PROTECTED]> [01-10-31 19:02]: >please can sombody tell me how to enable colors in mutt > >i have a color xterm and vim has colors in it > >what must i do for mutt ot work here also Do you have color statements in your ~/.muttrc? Go to www.mutt.org and look for examples of ~/.muttrc, many of them have colors. Thorsten -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin
Re: color
On Wed, 31 Oct 2001, Daniel Farnsworth Teichert wrote: > When I was first messing around with Mutt I had similar > troubles when trying to use a regular old xterm. It > seems like I found that setting the environment variable > TERM to color_xterm instead of just xterm made it work. > Calling xterm with the -tn color_xterm flag has a similar > effect, I think. color_xterm is similar to xterm-color, and both are incorrect for XFree86 xterm and rxvt (ditto Eterm and aterm, konsole and gnome-terminal). to see this, use infocmp to compare their terminfo entries. > > HTH > > --Daniel > > On Wed, Oct 31, 2001 at 06:02:17PM +, John J Kearney wrote: > > please can sombody tell me how to enable colors in mutt > > > > i have a color xterm and vim has colors in it > > > > what must i do for mutt ot work here also > > > > TIA JJK > -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
On Wed, 31 Oct 2001, René Clerc wrote: > * John J Kearney <[EMAIL PROTECTED]> [31-10-2001 19:01]: > > | please can sombody tell me how to enable colors in mutt > | > | i have a color xterm and vim has colors in it > | > | what must i do for mutt ot work here also > > Configure them in your .muttrc ;) > > See the 'color' section in `man muttrc`. i think i've it all set up in my muttrc i'm still new and using most of svens config but i can't get any color using XFree86 4.1.0(161) and Mutt 1.3.23.1i (2001-10-31) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: SunOS 5.5.1 (sun4m) Compile options: -DOMAIN +DEBUG -HOMESPOOL -USE_SETGID +USE_DOTLOCK -DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META -HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV +ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL="/usr/sharew/bin/ispell" SENDMAIL="/usr/lib/sendmail" MAILPATH="/var/mail" PKGDATADIR="/home/jkearney/appli/share/mutt" SYSCONFDIR="/home/jkearney/appli/etc" EXECSHELL="/bin/sh" -MIXMASTER To contact the developers, please mail to <[EMAIL PROTECTED]>. To report a bug, please use the flea(1) utility. it's gotta be somting stupid :| TIA > >
Re: color
> Date: Wed, 31 Oct 2001 13:56:52 -0500 (EST) > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > To: Daniel Farnsworth Teichert <[EMAIL PROTECTED]> > cc: <[EMAIL PROTECTED]> > Subject: Re: color > > On Wed, 31 Oct 2001, Daniel Farnsworth Teichert wrote: > > > When I was first messing around with Mutt I had similar > > troubles when trying to use a regular old xterm. It > > seems like I found that setting the environment variable > > TERM to color_xterm instead of just xterm made it work. > > Calling xterm with the -tn color_xterm flag has a similar > > effect, I think. > > color_xterm is similar to xterm-color, and both are incorrect for XFree86 > xterm and rxvt (ditto Eterm and aterm, konsole and gnome-terminal). If xterm-color is incorrect, what should the value be? BTW, 1.2.5 displayed colors in rxvt without this hack, 1.3.23i didn't display colors until I put rxtv.termName = xterm-color in my .Xdefaults. TIA -- FreeBSD 4.4-STABLE 10:30AM up 8 days, 21:13, 14 users, load averages: 0.06, 0.06, 0.02
Re: color
On 1 Nov 2001, John J Kearney wrote: > On Wed, 31 Oct 2001, René Clerc wrote: > > > * John J Kearney <[EMAIL PROTECTED]> [31-10-2001 19:01]: > > > > | please can sombody tell me how to enable colors in mutt > > | i have a color xterm and vim has colors in it > > | what must i do for mutt ot work here also > > Configure them in your .muttrc ;) > > See the 'color' section in `man muttrc`. > i think i've it all set up in my muttrc > > i'm still new and using most of svens config > but i can't get any color > > using XFree86 4.1.0(161) what $TERM are you using? (XFree86 xterm should be "xterm-xfree86"; its accompanying terminfo file would install that as "xterm"). -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
On Thu, 1 Nov 2001, Roman Neuhauser wrote: > If xterm-color is incorrect, what should the value be? > BTW, 1.2.5 displayed colors in rxvt without this hack, > 1.3.23i didn't display colors until I put > rxtv.termName = xterm-color in my .Xdefaults. did you use curses/ncurses or slang? rxvt sets $COLORTERM, which is used by slang to circumvent the normal setting of $TERM. -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
> Date: Thu, 1 Nov 2001 06:39:01 -0500 (EST) > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > To: Roman Neuhauser <[EMAIL PROTECTED]> > cc: <[EMAIL PROTECTED]> > Subject: Re: color > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > If xterm-color is incorrect, what should the value be? > > BTW, 1.2.5 displayed colors in rxvt without this hack, > > 1.3.23i didn't display colors until I put > > rxtv.termName = xterm-color in my .Xdefaults. > > did you use curses/ncurses or slang? > rxvt sets $COLORTERM, which is used by slang to circumvent the normal > setting of $TERM. I have installed mutt from the port with the default settings. Looking in the makefile doesn't reveal anything suspicious, so I guess mutt's chose either of them: ncurses is part of the base system on FreeBSD, and I have libslang 1.4.4_1 port installed too. $COLORTERM is rxvt-xpm, so I guess that indicates mutt is linked against ncurses, right? mutt -v: Mutt 1.3.23i (2001-10-09) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: FreeBSD 4.4-STABLE [using ncurses 5.1] Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE -USE_FCNTL +USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -HAVE_WC_FUNCS -HAVE_LANGINFO_CODESET -HAVE_LANGIFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL="/usr/local/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/local/share/mutt" SYSCONFDIR="/usr/local/etc" EXECSHELL="/bin/sh" -MIXMASTER TIA -- FreeBSD 4.4-STABLE 2:59PM up 9 days, 1:42, 18 users, load averages: 0.05, 0.12, 0.09
Re: color
On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > did you use curses/ncurses or slang? > > rxvt sets $COLORTERM, which is used by slang to circumvent the normal > > setting of $TERM. > > I have installed mutt from the port with the default settings. > Looking in the makefile doesn't reveal anything suspicious, so I > guess mutt's chose either of them: ncurses is part of the base > system on FreeBSD, and I have libslang 1.4.4_1 port installed too. > $COLORTERM is rxvt-xpm, so I guess that indicates mutt is linked > against ncurses, right? what was $TERM before you set rxvt.termName ? (your version summary says mutt is linked with ncurses 5.1, which sounds reasonable) -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
> Date: Thu, 1 Nov 2001 09:35:11 -0500 (EST) > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > To: Roman Neuhauser <[EMAIL PROTECTED]> > cc: <[EMAIL PROTECTED]> > Subject: Re: color > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > > > did you use curses/ncurses or slang? > > > rxvt sets $COLORTERM, which is used by slang to circumvent the normal > > > setting of $TERM. > > > > I have installed mutt from the port with the default settings. > > Looking in the makefile doesn't reveal anything suspicious, so I > > guess mutt's chose either of them: ncurses is part of the base > > system on FreeBSD, and I have libslang 1.4.4_1 port installed too. > > $COLORTERM is rxvt-xpm, so I guess that indicates mutt is linked > > against ncurses, right? > > what was $TERM before you set rxvt.termName ? just xterm. > (your version summary says mutt is linked with ncurses 5.1, which sounds > reasonable) heh, yes, I originally missed the System: line, and looked for it in the Compile options list. -- FreeBSD 4.4-STABLE 3:44PM up 9 days, 2:27, 14 users, load averages: 0.08, 0.14, 0.10
Re: color
On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > what was $TERM before you set rxvt.termName ? > > just xterm. "xterm" is usually the same as "xterm-r6" (no color). (but "xterm-color" isn't correct - would be nice if FreeBSD installed the correct termcap entries so this wasn't something I had to point out periodically). -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
> Date: Thu, 1 Nov 2001 10:54:42 -0500 (EST) > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > To: Roman Neuhauser <[EMAIL PROTECTED]> > cc: <[EMAIL PROTECTED]> > Subject: Re: color > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > > > what was $TERM before you set rxvt.termName ? > > > > just xterm. > > "xterm" is usually the same as "xterm-r6" (no color). > > (but "xterm-color" isn't correct - would be nice if FreeBSD installed the > correct termcap entries so this wasn't something I had to point out > periodically). I don't say it's correct. I _don't_ know the correct value. I've seen this suggested on freebsd-questions@, and it works. But if you tell me the correct value, I'll be happy to change the setting. -- FreeBSD 4.4-STABLE 6:18PM up 9 days, 5:01, 15 users, load averages: 0.18, 0.13, 0.09
Re: color
On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > Date: Thu, 1 Nov 2001 10:54:42 -0500 (EST) > > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > cc: <[EMAIL PROTECTED]> > > Subject: Re: color > > > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > > > > > what was $TERM before you set rxvt.termName ? > > > > > > just xterm. > > > > "xterm" is usually the same as "xterm-r6" (no color). > > > > (but "xterm-color" isn't correct - would be nice if FreeBSD installed the > > correct termcap entries so this wasn't something I had to point out > > periodically). > > I don't say it's correct. I _don't_ know the correct value. I've seen > this suggested on freebsd-questions@, and it works. But if you tell me > the correct value, I'll be happy to change the setting. Usually (except of course the suggestions which are secondhand or worse) the suggestion is based on the fact that FreeBSD doesn't install a termcap entry for anything more appropriate. There is a termcap file distributed with rxvt and one with XFree86 xterm. I'd start with those (preferring "rxvt" and "xterm-xfree86"). FreeBSD uses a compiled database for termcap, iirc under /usr/share/misc. Edit (save the original of course) the termcap file, putting the new entries at the beginning. Recompile the termcap database (I don't recall the name of the command - something like make_capdb - there is a manpage for it). There is also a better termcap file here (but doesn't necessarily include a few of the specialized console types for FreeBSD): ftp://invisible-island.net/ncurses/termcap.src.gz -- T.E.Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: color
> Date: Thu, 1 Nov 2001 13:20:53 -0500 (EST) > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > To: Roman Neuhauser <[EMAIL PROTECTED]> > cc: <[EMAIL PROTECTED]> > Subject: Re: color > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > > > Date: Thu, 1 Nov 2001 10:54:42 -0500 (EST) > > > From: "Thomas E. Dickey" <[EMAIL PROTECTED]> > > > To: Roman Neuhauser <[EMAIL PROTECTED]> > > > cc: <[EMAIL PROTECTED]> > > > Subject: Re: color > > > > > > On Thu, 1 Nov 2001, Roman Neuhauser wrote: > > > > > > > > what was $TERM before you set rxvt.termName ? > > > > > > > > just xterm. > > > > > > "xterm" is usually the same as "xterm-r6" (no color). > > > > > > (but "xterm-color" isn't correct - would be nice if FreeBSD installed the > > > correct termcap entries so this wasn't something I had to point out > > > periodically). > > > > I don't say it's correct. I _don't_ know the correct value. I've seen > > this suggested on freebsd-questions@, and it works. But if you tell me > > the correct value, I'll be happy to change the setting. > > Usually (except of course the suggestions which are secondhand or worse) > the suggestion is based on the fact that FreeBSD doesn't install a termcap > entry for anything more appropriate. > > There is a termcap file distributed with rxvt and one with XFree86 xterm. > I'd start with those (preferring "rxvt" and "xterm-xfree86"). FreeBSD > uses a compiled database for termcap, iirc under /usr/share/misc. Edit > (save the original of course) the termcap file, putting the new entries at > the beginning. Recompile the termcap database (I don't recall the name of > the command - something like make_capdb - there is a manpage for it). > > There is also a better termcap file here (but doesn't necessarily include > a few of the specialized console types for FreeBSD): > > ftp://invisible-island.net/ncurses/termcap.src.gz Hi Thomas, thank you for your answer. I don't know if it means anything, but my termcap already contained a rxvt entry, with a comment that it's taken from the rxvt-2.6.3 sources, which is what I use. I rebuilt the database just to be sure, commented out the rxvt.termName line in my .Xdefaults file, and opened a new terminal window (rxvt): roman@roman ~ > grep termName .Xdefaults ! rxvt.termName: xterm-color roman@roman ~ > echo $TERM xterm Next, I put the two rxvt entries (rxvt-basic and rxvt) from termcap.src.gz in my /usr/share/misc/termcap, and got these two messages upon issuing cap_mkdb: cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X Window System) cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X Window System) Whassup? Besides, termcap.src.gz says 'rxvt is normally configured to look for "xterm" or "xterm-color" as $TERM. Since rxvt is not really compatible with xterm, it should be configured as "rxvt" (monochrome) and "rxvt-color"'. What does that mean for me? Thank you for your patience. Roman -- FreeBSD 4.4-STABLE 12:26PM up 9 days, 23:09, 15 users, load averages: 0.71, 0.65, 0.57
Re: color
On Fri, Nov 09, 2001 at 08:16:34PM +0100, Roman Neuhauser wrote: > thank you for your answer. I don't know if it means anything, but my > termcap already contained a rxvt entry, with a comment that it's taken > from the rxvt-2.6.3 sources, which is what I use. I rebuilt the database > just to be sure, commented out the rxvt.termName line in my .Xdefaults > file, and opened a new terminal window (rxvt): > > roman@roman ~ > grep termName .Xdefaults > ! rxvt.termName: xterm-color > roman@roman ~ > echo $TERM > xterm > > Next, I put the two rxvt entries (rxvt-basic and rxvt) from > termcap.src.gz in my /usr/share/misc/termcap, and got these two > messages upon issuing cap_mkdb: > > cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X > Window System) > cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X > Window System) > > Whassup? offhand (I'm working on Linux now, will try to remember to test this on FreeBSD) I think it's complaining that the name cited in the "tc=" clause doesn't exist, e.g., "ecma+color": rxvt|rxvt terminal emulator (X Window System):\ :NC@:\ :me=\E[m\017:tc=rxvt-basic:tc=ecma+color: Also cap_mkdb may also complain that the termcap doesn't begin with a 2-character identifier. Canonical termcap entries begin that way; termcaps generated from infocmp don't do that. (I have a to-do item to add an infocmp option for this). > Besides, termcap.src.gz says 'rxvt is normally configured to look for > "xterm" or "xterm-color" as $TERM. Since rxvt is not really compatible > with xterm, it should be configured as "rxvt" (monochrome) and > "rxvt-color"'. What does that mean for me? What I do is edit the header-file in rxvt that's hardcoded to "xterm" and change that to "rxvt" when I compile it. (I don't recall that being configurable, and since it's easy to edit I haven't looked to see if there's a better way). Likewise, for the various other terminal emulators (I install those all to set $TERM to be what it "should" be, e.g., xterm-r5, xterm-r6, xterm-xfree86, kterm, aterm, Eterm, rxvt, since it's simpler to map those _to_ "xterm" on the remote side if needed than determine which flavor it really is. That reminds me of a bug that I observed in Mandrake 8.1 (you see, FreeBSD isn't the only one that can't setup terminfo properly): 011017 md81 installs xterm-debian as an alias for 'nxterm' and 'xterm-color', which looks like the 88b-version (so alternate screen stuff is a bit retarded). Actually, 'xterm' looks like the newer version, since it uses 1049. This termcap doesn't use the "tc=" clause: rxvt|rxvt terminal emulator (X Window System):\ :am:eo:km:mi:ms:xn:xo:\ :co#80:it#8:li#24:\ :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ :RI=\E[%dC:UP=\E[%dA:ae=^O:al=\E[L:as=^N:bl=^G:cd=\E[J:\ :ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cr=^M:\ :cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:ei=\E[4l:\ :ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=^H:kd=\E[B:ke=\E>:\ :kh=\E[7~:kl=\E[D:kr=\E[C:ks=\E=:ku=\E[A:le=^H:mb=\E[5m:\ :md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:sc=\E7:\ :se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ :te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:ue=\E[24m:up=\E[A:\ :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ :vs=\E[?25h: -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
color 'default'
Where does 'default' come from, as whether it gets recognized or not? I ended up installing ncurses into my home directory and mutt built perfectly. I reported this back the server admin and she said that after looking into it, ncurses on the server was indeed screwed. She said she reinstalled it, and when I tried building 1.3.28 just to try the server ncurses, it built fine, and mutt -v reports ncurses 5.2, but default is not recognized when it starts up. In the version I built from ncurses from my home dir, no problem. Thanks. -Ken
Header color
Hi All, How do I set the bg/fg color for the whole line, for a particular header field?? Not just for the header alone, but the whole line should have the same bg color?? How is this possible?? -- V Suresh - ANTI SPAM: http://india.cauce.org
background color
Hi all How can I set the background color ? I use mutt in a xterm with custom background color. I would like to keep this setting. Actually when I launch mutt he reset (to white) the background. The color I use in my xterm is not the «classic» color "#fbe6b3" (what I mean is the color is not in the default group color of mutt. Thanks. Regards. -- Albert SHIH SIO batiment 15 Observatoire de Paris Meudon 5 Place Jules Janssen 92195 Meudon Cedex Heure local/Local time: Mer 11 jui 2008 10:10:38 CEST
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
color limit?
I have 256 colors enabled for my urxvt, and all works well with mutt until I try to define more than 21 color specifications in .muttrc, the colors seem to get confused. Must be a table overflow or something. Should I engender a flea? Or is this already known? I tried searching the flea database without success. -- Sterling (Chip) Camden| sterl...@camdensoftware.com | 2048D/3A978E4F http://camdensoftware.com | http://chipstips.com| http://chipsquips.com pgp7g2PQ6cCCf.pgp Description: PGP signature
Re: Header color -> color header fg bg regexp
* V_Suresh <[EMAIL PROTECTED]> [2002-07-25 08:09]: > How do I set the bg/fg color for the whole line, for a particular > header field?? Not just for the header alone, but the whole line > should have the same bg color?? How is this possible?? color header fg bg regexp examples: http://www.math.fu-berlin.de/~guckes/setup/mutt.color.header* Sven -- Sven [EMAIL PROTECTED] Sample Color Setup for Mutt: MUTT http://www.math.fu-berlin.de/~guckes/setup/mutt.color.body WOOF!,, MUTT http://www.math.fu-berlin.de/~guckes/setup/mutt.color.header (__/'. MUTT http://www.math.fu-berlin.de/~guckes/setup/mutt.color.index /| |\
Re: Header color -> color header fg bg regexp
* On Thu, 25 Jul 2002, Sven Guckes wrote: > * V_Suresh <[EMAIL PROTECTED]> [2002-07-25 08:09]: > > How do I set the bg/fg color for the whole line, for a particular > > header field?? Not just for the header alone, but the whole line > > should have the same bg color?? How is this possible?? > > color header fg bg regexp I think he means that this command is only coloring to the end of the last word in the header and not all the way to the end of the line on his screen. I noticed this behavior before, too, and when I switched from ncurses to s-lang, it started doing the whole line. It may depend on terminal settings or something else, too? -- John
Re: Header color -> color header fg bg regexp
On Thu, Jul 25, 2002 at 02:35:34PM -0700, John Iverson wrote: > * On Thu, 25 Jul 2002, Sven Guckes wrote: > > > * V_Suresh <[EMAIL PROTECTED]> [2002-07-25 08:09]: > > > How do I set the bg/fg color for the whole line, for a particular > > > header field?? Not just for the header alone, but the whole line > > > should have the same bg color?? How is this possible?? > > > > color header fg bg regexp > > I think he means that this command is only coloring to the end of > the last word in the header and not all the way to the end of the > line on his screen. I noticed this behavior before, too, and > when I switched from ncurses to s-lang, it started doing the > whole line. > > It may depend on terminal settings or something else, too? either that (not choosing a terminal type that tells whether it can clear using the background color), or one of the cases where mutt doesn't setup the curses calls properly -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Re: Header color -> color header fg bg regexp
--VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alas! Thomas Dickey spake thus: > On Thu, Jul 25, 2002 at 02:35:34PM -0700, John Iverson wrote: > > I think he means that this command is only coloring to the end of > > the last word in the header and not all the way to the end of the > > line on his screen. I noticed this behavior before, too, and > > when I switched from ncurses to s-lang, it started doing the > > whole line. > >=20 > > It may depend on terminal settings or something else, too? >=20 > either that (not choosing a terminal type that tells whether it can clear > using the background color), or one of the cases where mutt doesn't > setup the curses calls properly This has come up before; I could be wrong, but I thought the general consensus was that ncurses won't do the whole line, while slang does. Maybe I'm imagining things, though ;) --=20 Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- A university is what a college becomes when the faculty loses interest in students. -- John Ciardi --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9QH8SPTh2iSBKeccRAj/bAJsHnbaH35du2pstfax2mlXbf42MYwCdHQE+ xyjP2PB/jGgeR9E1vQdu4dE= =xUmd -END PGP SIGNATURE- --VS++wcV0S1rZb1Fb--
Re: Header color -> color header fg bg regexp
On Thu, Jul 25, 2002 at 04:43:30PM -0600, Rob 'Feztaa' Park wrote: > This has come up before; I could be wrong, but I thought the general > consensus was that ncurses won't do the whole line, while slang does. > Maybe I'm imagining things, though ;) no - the issue (for mutt/ncurses) is whether mutt calls the functions that tell ncurses to fill the line with the background color. I pointed out some of those a couple of years ago to someone who submitted patches for mutt, while some other cases were less obvious. -- Thomas E. Dickey <[EMAIL PROTECTED]> http://invisible-island.net ftp://invisible-island.net
Solaris2.6/xterm/color?
At work i am at solaris 2.6. I am no sysop. The system uses terminfo (as far as i can tell). I do have a local installation of XFree86 and ncursus. However i can't get mutt to start up inside xterm with colors. I know this isnt something with mutt, but something with my xterm (terminfo) settings. Anyone here know how i can get my fancy colors, like i have on my linux box at home?? Thanks, jan
Sample Color Schemes?
Does anyone have some good looking color schemes? I tried a few that I found on the web, they were pretty awful... Thanks, A. (mutt.themes.org anyone?) -- Adam Sherman <[EMAIL PROTECTED]> +1 (613) 223-5746
color in mutt
When i run mutt remotely from my BSD box, i use an xterm and color is no problem. However, when i use the console (TERM=cons25) or when i run it in EasyTerm here on w95 at work, i get problems. Obviously vt100 does not support color. I know cons25 shows color when i use colorls, but i can't get it to work remotely with mutt in color. When i run mutt over EasyTerm, vt100 has no color but setting TERM= xterm-color messes up the screen display. (There seems to be an extra line of text showing up in odd places, like across the top or bottom of the screen. -=> jm <=- Please CC me on all replies --- "The light that burns twice as bright burns half as long, and you have burned so very, very brightly."
Help with color
I have these lines: color index brightwhite default * color index yellow default '~l' color index brightyellowdefault '~N ~l' in my .muttrc file. As most of you know, messages that are from a list (defined in .muttrc) are yellow. "New" list messages are bright yellow. My problem is after the message has been read, it changes to a color that makes the text literally illegible. This may be related to my mutt window (under X-Windows) being an Eterm window with an image background. Regardless, I want to know how to define a color for "read" "list" messages. How do I do that ?? I *tried* this: color index green default '~R ~l' I made an assumption that "~R" would get "read" messages... but I was wrong. ;-) Any help is appreciated. Regards, Hall
Muttrc color question
Is it possible to specify a foreground color as transparent? Essentially, I'd like pretty much all my colors as default except for indicator which should be reversed: foreground should be bg's default and vice-versa. Is this possible? -- jeremy ... and never, ever play leapfrog with a unicorn.
default color definition
hi all, i am trying to get mutt to work with a transparent wterm. however, when i chose 'default' as the background color for each of my color defintions, mutt chokes when loading. it complains about an invalid color or something like that. yes the manual shows it is an acceptable option. any ideas? i am running mutt 1.0.1 jm -- - Jonathon McKitrick -- [EMAIL PROTECTED] Break free of The Matrix. Switch to FreeBSD. -
default color definition
hi all, i am trying to get mutt to work with a transparent wterm. however, when i chose 'default' as the background color for each of my color defintions, mutt chokes when loading. it complains about an invalid color or something like that. yes the manual shows it is an acceptable option. any ideas? i am running mutt 1.0.1 jm -- - Jonathon McKitrick -- [EMAIL PROTECTED] Break free of The Matrix. Switch to FreeBSD. -
default color definition
hi all, i am trying to get mutt to work with a transparent wterm. however, when i chose 'default' as the background color for each of my color defintions, mutt chokes when loading. it complains about an invalid color or something like that. yes the manual shows it is an acceptable option. any ideas? i am running mutt 1.0.1 jm -- - Jonathon McKitrick -- [EMAIL PROTECTED] Break free of The Matrix. Switch to FreeBSD. -
Re: Mutt & Color
Hi, Jerry Walsh typed: > I want to add color support to MUTT > the error it gives is: > Error in /home/jerry/.muttrc, line 29: color: unknown command Type in mutt -v. See if you have +HAVE_COLOR or -HAVE_COLOR (most probably the latter). Your ncurses version must be old - upgrade that and run configure for mutt again. http://dickey.his.com/ncurses/ncurses.html -- Mrinal Kalakrishnan <[EMAIL PROTECTED]> http://mrinal.dhs.org/ Linux 2.2.16 || PGP:B1E86F5B || Mutt 1.3.4i (2000-06-19) || VIM 5.6 -- "World domination. Fast" (By Linus Torvalds)
Re: Mutt & Color
On Tue, Jul 04, 2000 at 02:25:00PM +0100, Jerry Walsh wrote: > I want to add color support to MUTT we just answered this on Saturday (which spawned a new thread about needing an FAQ). What dependencies does that port have? -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Problem with color
I know this is a FAQ, but I tried everyhting in the FAQ itself and I couldn't solve my problem. I'm trying to compile mutt 1.2.5i on RedHat 6.0 with either ncurses or slang, I don't care. I just want color! RedHat's mutt versions don't have color and so I tried compiling it from the tarball on mutt.org. It compiles and runs fine, but no color. Just black text on white background for any library, any #defines I manipulate in acconfig.h, any terminal mode I want including linux, nothing seems to work. after configure runs, config.h includes HAVE_COLOR #defined in it. So I know configure is working, and checking the source (specifically color.c) I don't know what could not be working here. I also tried compiling with slang and setting COLORTERM; no such luck. Maybe I should just sneak onto the system in the middle of the night and install Debian; it has a color mutt package :-) On that topic, I have been able to get mutt to display color on the same terminal on the same machine with the same $TERM when logged into my home machines with Debian and mutt. I also just tried upgrading to ncurses 5.0 in case there was some incompatibility; didn't work. - Ben Roberts, Class of 2001 (1st of millenium), founding member of MBLUG "If your motherboard smells like carcinogens it's time to get a new motherboard." -- Ben Roberts, refering to his SPARC
Re: more color
On 26, Oct, 2000 at 12:11:44AM -0700, Mike E wrote: > Okay, previously I had a problem with color, and it was resolved > that I was using a version of ncurses that was too old. > > On another server (OpenBSD 2.7) I've compiled mutt to test it out. > Here is my mutt -v output: > > ~ $ mutt -v > Mutt 1.2.4i (2000-07-07) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: OpenBSD 2.7 [using ncurses 5.0] > Compile options: > -DOMAIN > -DEBUG > -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK > -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/mail" > SHAREDIR="/usr/local/share/mutt" > SYSCONFDIR="/usr/local/etc" > -ISPELL > To contact the developers, please mail to <[EMAIL PROTECTED]>. > To report a bug, please use the muttbug utility. > > I have +HAVE_COLROR and ncurses 5.0. However color still isn't > working. I get no .muttrc errors on my color commands when running > mutt, and color works in other programs (like BitchX), so I'm pretty > stumped. Anyone have any ideas? A slightly long shot: what's your ~/muttrc||/etc/muttrc saying? Or maybe you've copied your old one with nice colors and all from an older version (though I think that would produce errors ...), if so it might be because you are using vt220 and not pcvt25 terminal drivers, but then again, you get colors with BitchX, so that's not it I guess ... I run mutt-1.2.5 on OpenBSD-current, and I get colors in both xterm and when I puTTY to it from work, so it can work. Hope this helps a little, HAND Morten -- UNIX, reach out and grep someone!
Re: more color
On Thu, Oct 26, 2000 at 12:11:44AM -0700, Mike E wrote: > I have +HAVE_COLROR and ncurses 5.0. However color still isn't > working. I get no .muttrc errors on my color commands when running > mutt, and color works in other programs (like BitchX), so I'm pretty > stumped. Anyone have any ideas? your terminal description probably doesn't do color (BitchX may be linked with slang, which has hardcoded a particular variation of termcap/terminfo support for color that works for rxvt). There are a number of choices for your $TERM variable. The current version of ncurses is 5.2 (20001021) There's an faq at http://dickey.his.com/ncurses/ncurses.faq.html -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
Re: color quotes
On 1 February 1999, Daniel Bauke <[EMAIL PROTECTED]> wrote: > I've found another (I think, well-known) `funny feature'. When not > all level of quotes fits the first screen and they start from `the > oldest', mutt's changing colors of next (`newer') ones when they > appear. [...] > Shouldn't mutt search whole message for `>', next for `> >', next > `> > >' and so on and after that color quotes depending gathered > information? No. Parsing the whole message before displaying it would be basically equivalent to the "bottom" function, which would be annoyingly slow for most messages. BTW, Mutt doesn't just count the '>', if it did it wouldn't be able to catch Emacs-style quotes "User>". > It could slow down viewing each letter, but ``every good thing comes > with a price'' ;-). Maybe this price's not so high? You can emulate this behaviour with macros, just issue a "bottom" and a "top" when you enter the pager. Slower than just "bottom". :-) Regards, Liviu Daia -- Dr. Liviu Daia e-mail: [EMAIL PROTECTED] Institute of Mathematics web page: http://www.imar.ro/~daia of the Romanian Academy PGP key: http://www.imar.ro/~daia/daia.asc
Re: subject color
Ayman Haidar on Thu 18/03 22:46 -0500: > I was wondering if it's possible to color the title of an email > message like: > >1 b Mar 18 To LUG ( 13) [WLUG] nslookup > ^^^ > | > different color Short answer: no. Long answer: none of the current developers care for this feature, so it probably won't get coded unless someone feels like doing it. I've wanted this for a long time but your post makes me want to code it :) I think I will try if I get some time. Feature: specify coloring of the various `%' conversions used in index_format. What I'm thinking is to add "color" commands for each % conversion; ie, one could "color index_s brightgreen black" to acheive that color for the subject expansion in index. If `index_x' (where `x' is the format conversion letter) is unset, then the `index' color would be used for that field, and `index' would always be used for field delimiters. An alternative would be to specify the color *in* the $index_format string, but this seems wrong to me since the code should probably be kept separate. I've not looked around at that part of the source yet, but I invite comments about this; there's a strong chance I might code this in my freetime (basically none so it will be a while :) -- Scott
Re: tag color
On Thu, 13 May 1999, I.D. Chan wrote: > How could set the color of the tagged messages ? > > I could find out the way to do that. color index magentadefault ~T # Tagged Ciao Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ * PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Re: tag color
Hi, On Thu, May 13, 1999 at 16:44 +0800, I.D. Chan wrote: > How could set the color of the tagged messages ? Try something like color index brightblue white ~T Ciao, Stefan
Re: Color Issues
Warning Could not process message with given Content-Type: multipart/signed; boundary=VbJkn9YxBvnuCH5J; micalg=pgp-md5;protocol="application/pgp-signature"
Re: Color Issues
Mark: I connect to my Linux box from home with Data Fellow's SSH2 client for Win9x, and it too has an option to display ANSI colors. I also had trouble displaying color Mutt, until I tried this: Once you connect, try TERM=rxvt export TERM mutt You might get a few characters displaying oddly (such as the thread indicators), but colors come through well (at least for me). If it works for you, you can set add these lines to your .bashrc or /etc/profile, etcetera. It will detect when you're connecting on a pseudo-tty, and adjust the terminal type accordingly. Your mileage may vary. V_TERMINAL=`tty` case "$V_TERMINAL" in /dev/ttyp*) TERM="rxvt";; *) TERM="linux";; esac export TERM Good luck! -- Don On Tue, May 18, 1999 at 03:19:54PM -0400, Mark D. Scudder wrote: ...I connect to my Linux box using SecureCRT (an ssh client for Win95) and if I set up as VT100 with "ANSI Color" on, I can see color objects such as Linux's directory colors. But Mutt doesn't work. I tried creating the term files like it says in the FAQ but it's obvious they're made for an xterm window and not a terminal emulator. However, I'd like to think that if Linux itself can do color, so can Mutt. Don S. Rogers . Department Computing Coordinator Brown University . Sociology . Population Studies Social Science Research Lab . http://ssrl.pstc.brown.edu phone 401.863.2550 . fax 401.863.3213
Re: Color Issues
le 18 May, Mark D. Scudder a écrit :
> Hello,
>
> I've been using Mutt for a few weeks now and I like it. However, one of
> the reasons I did start using it was so I could have a color mail client
> for Linux. I connect to my Linux box using SecureCRT (an ssh client for
> Win95) and if I set up as VT100 with "ANSI Color" on, I can see color
> objects such as Linux's directory colors. But Mutt doesn't work.
>
> I tried creating the term files like it says in the FAQ but it's obvious
> they're made for an xterm window and not a terminal emulator. However,
> I'd like to think that if Linux itself can do color, so can Mutt.
>
> I'd appreciate any help anybody could give, having a black-and-white
> e-mail program is such a drag :-).
>
> Mark
I personally set the TERM environment variable to xterm-color. This works fine
on a Linux machine, and also when I'm connected via PuTTY (another telnet/ssh
client for Win95)
Btw, does anyone know if it is possible to configure (as a single user) SunOS
5.5.1 (don't know if the version matters much) to enable coloring in mutt?
xterm-color is not recognized.
--
___
{~._.~}Renaud COLINET |
( Y ) [EMAIL PROTECTED] |
()~*~()01 48 42 22 80 (dom) |
(_)-(_)01 41 75 31 37 (bur) |
Re: Color Issues
On Wed, May 19, 1999 at 06:09:46PM +0200, Renaud Colinet wrote: > > Btw, does anyone know if it is possible to configure (as a single user) SunOS > 5.5.1 (don't know if the version matters much) to enable coloring in mutt? > xterm-color is not recognized. You'll have to install something that can deal with colors (I use Tom Dickey's xterm from http://www.clark.net/pub/dickey/xterm) since the usual Slugaris xterm can't do color. -- Brian Moore | "The Zen nature of a spammer resembles Sysadmin, C/Perl Hacker | a cockroach, except that the cockroach Usenet Vandal | is higher up on the evolutionary chain." Netscum, Bane of Elves. Peter Olson, Delphi Postmaster
Re: color question
On Wed, Oct 13, 1999 at 09:52:10PM -0700, Larry McVoy wrote: > However, one feature that I had that I really miss is this: I could have a > list of addresses and have color highlighting in the index based on those > addresses. Mutt has support for mailing lists, but that - while useful - > isn't what I want. A simple version of what I want is that all messages > sent to "lm@*" or CC-ed to are highlighted with a color on the index page. Check out `color' in the manual (you'll also want to see section 4.2. `Patterns'). This should do the trick: color index brightyellow blue "~C ^lm@" > Is there a way to do this? And is there a way to have an arbitrary list > of those? It's really useful. I get between 300-1000 messages a day and > I really want to be able to pick through and get the stuff that is to me > highlighted. I have this bad habit of cleaning out my mailbox early in > the morning before coffee. You can imagine the need for the highlighting... I have the same habit too (though I get substantially less messages a day). ;) You might also like mutt's `limit' command (I just love it). Also, sorting by `threads' and then by `to' helps with mailing lists a lot (I wish there were an option to sort by `list'...) Marius Gedminas -- "Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)" (Linus Torvalds, about his failing hard drive on linux.cs.helsinki.fi)
Re: color question
At 21:52 -0700 13 Oct 1999, Larry McVoy <[EMAIL PROTECTED]> wrote: > Is there a way to do this? And is there a way to have an arbitrary list > of those? It's really useful. I get between 300-1000 messages a day and > I really want to be able to pick through and get the stuff that is to me > highlighted. I have this bad habit of cleaning out my mailbox early in > the morning before coffee. You can imagine the need for the highlighting... There's already been an answer on how to color highlight messages addressed to an address which matches a regexp , but you can also color messages addressed to any address that matches $alternates: color index red black ~p Of course, it should also be mentioned that mutt already indicates which messages are to one of your addresses by putting one of the characters from $to_chars to the left of the date in the default $index_format. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Let us be charitable, and call it a misleading feature :-) --Larry Wall
no such color
seniors, i tell mutt to use color "default", but mutt tell me "default: no such color", why? for example "color error brightred default" Thanks
color in Eterm
seniors, i assign colors to mutt, then run it under console, the colors work. but run it under Eterm, colors didn't work. (colors of slrn work under Eterm) what did i miss to mutt under Eterm? my Eterm version 0.8.9 thanks reed
Re: Color xterm??
On Sat, Nov 13, 1999 at 10:39:18PM -0500, Subba Rao wrote: > Is color xterm a requirement for mutt's color feature? > I am using Slackware 4. The "ls" command has several color > options, where I see a different color for each file type. > If this xterm works for "ls" with color, then mutt's got to > work too. I have installed ncurses-5.0 and that is not helping > either. > > Any pointers to get colors working... Try: export TERM=exterm-color if using bash. > Subba Rao > [EMAIL PROTECTED] > http://pws.prserv.net/truemax/ -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: Color xterm??
At 10:39 PM 1999/11/13 -0500, you wrote: >Is color xterm a requirement for mutt's color feature? >...work too. I have installed ncurses-5.0 and that is not helping >either. to make mutt to work with color, set environment var TERM=xterm-color or TERM=rxvt, but these will cause some programs cannot be run (such as elvis) so, if you use Eterm, you can issue command "Eterm --term-name xterm-color -e mutt..." you also must to change the default maile editor of mutt to which can work in color terminal. good luck reed
Re: Color xterm??
> >How can I force mutt to use it's editor in the configuration file? in .muttrc, set editor=emacs(at your fave) :)
