Re: Color messages in the index view dynamically

Thanks Ed. In case someone else is interested in setting this up too, here is where I am so far. Having the messages in the maildir format on my side, I regularly (upon new message arrival using Mutt's $new_mail_command, and also once a day) scan the To-do folder with a script (here is a

Re: Color messages in the index view dynamically

I can get you part of the way, but someone else will have to help with the last part (if it's possible at all). I have mutt set up to use a different index_format on a per-message basis, so that I can see more detailed time information for messages that are newer, and courser and courser as

Re: Color display question

> I think that might be elinks. I'm not sure about what all the relevant > options are, but document.colors.text (default foreground) may be what > is giving you light gray text. You probably also want > document.colors.use_document_colors to be 2 and document.css.enable to > be enabled (1)?

Re: Color display question

On 2021-07-21, isdtor wrote: > I realize my config has a lot of moving parts and non-default > settings, but I still hope someone can shine a light on this. > > I use less instead of the internal pager (note -R option), > > set pager="less -eiMR" > > and elinks for html display > > text/html;

Re: color of unknown object

Hi Matthias, that might be: color compose header fgcolor bgcolor Best, JJ On 2020-12-07 08:01, Matthias Apitz wrote: Hello, I'm struggling with a color problem in mutt 2.0.2: In the last menu before sending the mail: -

Re: Color headers in pager based on message patterns

On 07Feb2018 20:35, Scott Kostyshak wrote: Example (untested): message-hook . 'set my_hdr_colour=green' message-hook ~p!~l 'set my_hdr_colour=yellow' message-hook . 'color header $my_hdr_colour default' so that a colour is chosen per message, then applied to your

Re: Color headers in pager based on message patterns

On Wed, Feb 07, 2018 at 10:00:33PM +, Cameron Simpson wrote: > On 07Feb2018 01:05, Scott Kostyshak wrote: > > I would like to color all header lines in the pager if a message pattern > > matches. > > > > As an example, I can use the following to color the index if a

Re: Color headers in pager based on message patterns

On 07Feb2018 01:05, Scott Kostyshak wrote: I would like to color all header lines in the pager if a message pattern matches. As an example, I can use the following to color the index if a message was sent to me and not sent to a list: color index yellow black ~p!~l But I

Re: color line in compose menu?

On Sun, Feb 12, 2017 at 06:22:20PM +0100, ilf wrote: > Kevin J. McCarthy: > > > I am trying to color the "Security:" line in the compose menu. Is > > > that possible? > > Sorry ilf, that part is not currently colorable. > > Okay, that's what I assumed. > > What do you think of this idea? Does it

Re: color line in compose menu?

Kevin J. McCarthy: I am trying to color the "Security:" line in the compose menu. Is that possible? Sorry ilf, that part is not currently colorable. Okay, that's what I assumed. What do you think of this idea? Does it sound useful to you? I for one would really like a color setting there,

Re: color line in compose menu?

On Sat, Feb 11, 2017 at 04:29:01PM +0100, ilf wrote: > I am trying to color the "Security:" line in the compose menu. Is that > possible? Sorry ilf, that part is not currently colorable. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc

Re: color messages in index that are sent directly to me (not from list)

On Wed, Dec 30, 2015 at 5:43 AM, Francesco Ariis wrote: > On Wed, Dec 30, 2015 at 05:06:07AM -0500, Xu Wang wrote: >> I am part of many mailing lists. I would like to know when: >> >> 1. I am CC'ed or in the To field of an email address >> 2. When (1) is true *and* there is no

Re: color messages in index that are sent directly to me (not from list)

On Wed, Dec 30, 2015 at 05:06:07AM -0500, Xu Wang wrote: > I am part of many mailing lists. I would like to know when: > > 1. I am CC'ed or in the To field of an email address > 2. When (1) is true *and* there is no mailing list in the CC or To field. > > (2) is specifically important to me

Re: Color changed in mutt

On Sat, Nov 30, 2013 at 12:25:42PM -0800, fe...@crowfix.com wrote: ...recently upgraded a few packages... ... Is this a known change in 1.5.22? What else could cause this change? I didn't see any 'color' notes in ChangeLog or NEWS. The colors in mutt are AFAIK just names of ANSI color codes,

Re: Color changed in mutt

On Sat, Nov 30, 2013 at 10:10:46PM +0100, Edward Toroshchin wrote: I strongly suspect that your terminal emulator has been updated together with mutt, and it now renders the colors differently. I almost always use mutt from within screen. Screen last changed 2012-11-20, and I rebooted for the

Re: Color changed in mutt -- Not a mutt problem

As I mentioned in another post, I had also changed company Mac laptops which I use to ssh in and run screen. I have now found that git diff by itself dumps all sorts of uninterpreted ESC sequences to the screen, but if I pipe that into less (git diff|less), less eats them up. The Mac 10.old

Re: color does not work

Quoth stardiviner on Thursday, 23 June 2011: problem: my color scheme can work before. But not, it can not work any more. all of mails in index are white, and mail context are white too. weird. I set some colors about index and body. I know it is fucking bad to say weird. Here is my

Re: color limit?

On Wed, Jul 21, 2010 at 02:02:56PM -0700, Chip Camden wrote: Quoth Chip Camden on Wednesday, 21 July 2010: 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

Re: color limit?

Quoth Chip Camden on Wednesday, 21 July 2010: 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

Re: color limit?

On Wed, Jul 21, 2010 at 01:53:58PM -0700, Chip Camden wrote: 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

Re: color limit?

Quoth Michael Elkins on Wednesday, 21 July 2010: On Wed, Jul 21, 2010 at 01:53:58PM -0700, Chip Camden wrote: 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

Re: color about w3m viewing in mutt

On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote: * peng shao on Tuesday, March 16, 2010 at 05:00:03 -0400 Because you w3m -dump to standard output -- or in this case to Mutt's pager. Okay I see, thanks. With lynx -dump? I doubt it. I use text/html; lynx -dump

Re: color about w3m viewing in mutt

On Tue, Mar 16, 2010 at 6:12 AM, peng shao shallp...@gmail.com wrote: On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote: much. But for me there is still some drawback, the %{charset} is lost :( Is there any possibility if I set autoview as off, and when I read an email,

Re: color about w3m viewing in mutt

* peng shao on Tuesday, March 16, 2010 at 06:12:02 -0400 On Tue, Mar 16, 2010 at 5:44 AM, Christian Ebert blacktr...@gmx.net wrote: With lynx -dump? I doubt it. I use text/html; lynx -dump -force_html -assume-charset=%{charset} %s; needsterminal; copiousoutput; in the mailcap and set

Re: color about w3m viewing in mutt

On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote: Mmh, you could create an addional mailcap file and toggle the $mailcap_path variable. Try the following (untested): set my_lynx_cap=/path/to/lynxmailcap macro pager K1 \ enter-command set

Re: color about w3m viewing in mutt

On 2010-03-16, peng shao shallp...@gmail.com wrote: On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote: Mmh, you could create an addional mailcap file and toggle the $mailcap_path variable. Try the following (untested): set my_lynx_cap=/path/to/lynxmailcap

Re: color about w3m viewing in mutt

On Tue, Mar 16, 2010 at 10:32 AM, Gary Johnson garyj...@spocom.com wrote: On 2010-03-16, peng shao shallp...@gmail.com wrote: On Tue, Mar 16, 2010 at 7:21 AM, Christian Ebert blacktr...@gmx.net wrote: d. The pipe is allowed here.  If you are getting an error message from using that rule, the

Re: color configuration setup

On Wed, Jan 13, 2010 at 07:47:08PM -0400, Monte Stevens wrote: On Wed, Jan 13, 2010 at 04:54:29PM -0500, Haines Brown KB1GRM ET1 wrote: I'm running mutt on debian and within emcas. I have emcacs set up so that the keybinding M-C-m opens mutt in emacs. The problem is that I can't get this

Re: color configuration setup

On Thu, Jan 14, 2010 at 06:37:52AM -0500, Haines Brown KB1GRM ET1 wrote: On Wed, Jan 13, 2010 at 07:47:08PM -0400, Monte Stevens wrote: On Wed, Jan 13, 2010 at 04:54:29PM -0500, Haines Brown KB1GRM ET1 wrote: I'm running mutt on debian and within emcas. I have emcacs set up so that the

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

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

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

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

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.

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

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

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

Re: color of indicator bar

* Rocco Rutte [EMAIL PROTECTED] [2002-07-17 14:39 +0200]: I remember to have a read about about a patch making the indicator bar always exactly the same color as specified. The problem is that if the color of the message in the index is ``bright...'', the foreground color of the bar gets

Re: color of indicator bar

On Wed, Jul 17, 2002 at 02:39:20PM +0200, Rocco Rutte wrote: Hi, I remember to have a read about about a patch making the indicator bar always exactly the same color as specified. The problem is that if the color of the message in the index is ``bright...'', the foreground color of the bar

Re: Color with folder-hooks and status changes

I beleive the color used depends on the *last* matching color index statement, so you might have to include the ~D, ~F, and ~T ones in your folder-hook *after* the ~f one. No amount of reordering seemed to solve the problem, I've tried N different combinations (likely missing the right one of

Re: Color with folder-hooks and status changes

* On Fri, 07 Jun 2002, Joseph Ishac wrote: No amount of reordering seemed to solve the problem, I've tried N different combinations (likely missing the right one of course :) What I was originally thinking was not just reordering what you had, but also moving the ~D, ~F, and ~T into your

Re: Color with folder-hooks and status changes

Actually, I wasn't aware you could do that with the folder-hook command. :) However, I did a quick copy/paste on the lines below and it didn't remedy the problem. I think I'll stick with the four term expression with the use of ~P (which I didn't know about either). Thanks again for the help.

Re: Color with folder-hooks and status changes

* Joseph Ishac [EMAIL PROTECTED] [2002-06-07 15:11]: Actually, I wasn't aware you could do that with the folder-hook command. :) However, I did a quick copy/paste on the lines below and it didn't remedy the problem. I think I'll stick with the four term expression with the use of ~P (which

Re: Color with folder-hooks and status changes

* On Fri, 07 Jun 2002, Joseph Ishac wrote: Actually, I wasn't aware you could do that with the folder-hook command. :) However, I did a quick copy/paste on the lines below and it didn't remedy the problem. Works as intended here -- maybe you had other 'color index' commands which were

Re: Color with folder-hooks and status changes

* On Thu, 06 Jun 2002, Joseph Ishac wrote: The desired effect would be to have the behavior of the hooks as well as always changing color for status changes (such as tagging, etc.) I beleive the color used depends on the *last* matching color index statement, so you might have to include the

Re: color depending on To:

On Sun, Apr 28, 2002 at 08:19:19PM -0700, John Iverson wrote: Actually, it was me who was missing something. I'm using color index to match my old addresses, not color header. So I'm coloring the matched messages in the index, rather than coloring the headers in the pager. Sorry about

Re: color depending on To:

[29.04.02 01:45:36% +] Flavien -- : What I'm trying to match are headers like : Subject: Blah blah To: My Friend [EMAIL PROTECTED], Another [EMAIL PROTECTED], [EMAIL PROTECTED], Flavien [EMAIL PROTECTED], Joe Foobar [EMAIL PROTECTED], x [EMAIL PROTECTED], [EMAIL PROTECTED]

Re: color depending on To:

* Flavien [EMAIL PROTECTED] [2002-04-28 17.36 +0200]: Hello, Hi. I have som old addresses that some people still have in their address-books. I'd like to spot these people by colorizing the headers when matching one of those addresses. It works pretty well with : [...snip...]

Re: color depending on To:

Hi, * Flavien [04/28/02 17:36:10 CEST] wrote: I have som old addresses that some people still have in their address-books. I'd like to spot these people by colorizing the headers when matching one of those addresses. It works pretty well with : color header red black

Re: color depending on To:

* On Sun, 28 Apr 2002, Flavien wrote: I have som old addresses that some people still have in their address-books. I'd like to spot these people by colorizing the headers when matching one of those addresses. It works pretty well with : color header red black

Re: color depending on To:

Hi, John Iverson gave the following hint : I use ~C for this and it seems to work fine, even when the address isn't on the first line of the To: header. Try this: color header red black ~C myoldlogin\@myoldaddress\.com I must be missing something. It does not work here... :-( I daily

Re: color depending on To:

* On Mon, 29 Apr 2002, Flavien wrote: I must be missing something. It does not work here... :-( Actually, it was me who was missing something. I'm using color index to match my old addresses, not color header. So I'm coloring the matched messages in the index, rather than coloring the

Re: color 'default'

On Fri, 15 Mar 2002, Ken Weingold wrote: Where does 'default' come from, as whether it gets recognized or not? for ncurses, it's implemented by the use_default_colors() function. If the configure script doesn't find that, it won't compile-in the support for default into mutt. I ended up

Re: Color mails which are a reply to a mail from me?

Hi, Justin, How about sharing your 'regex' here for our reference? I've tried to write one but found it's inefficient due to searching in all the message bodies (~b). How do you think about it? * Is it possible to limit the lines to scan for message body? I think only 5 lines at the top and

Re: Color mails which are a reply to a mail from me?

Charles Jie muttered: BTW, I found I can not handle mutt's regexp though I'm an experienced Perl programmer. :) color index red default '~b (Charles|Charlie)' = Unmatched ( not to mention: color index red default '~b Charl(es|ie)' = Unmatched ( * Could anybody explain mutt's

Re: Color mails which are a reply to a mail from me?

[ I've moved quoted text around, so that it's in the correct place. ] At 20:39 +0800 12 Jan 2002, Charles Jie [EMAIL PROTECTED] wrote: On Sat, Jan 05, 2002 at 06:25:05PM -0600, Aaron Schrab wrote: color index red default ~b ^^ Would you please tell me

Re: Color mails which are a reply to a mail from me?

Thus spake Michael Tatge ([EMAIL PROTECTED]): You have to escape the pipe Symbol i.e. color index red default '~b Charl(es \| ie)' I never did figure that out. I just used my first time, since it is uncommon enough on my lists. Now, however, I use the References: header thusly:

Re: Color mails which are a reply to a mail from me?

At 20:34 -0500 05 Jan 2002, parv [EMAIL PROTECTED] wrote: in message [EMAIL PROTECTED], wrote Aaron Schrab thusly... color index red default %~P aaron, i have been using similar syntax for the same purpose since mutt v1.2.something (less than 1.2.4 for sure) created from freebsd

Re: Color mails which are a reply to a mail from me?

Thus spake Gerhard Siegesmund ([EMAIL PROTECTED]): I don't know if it is at all possible, but I loved this feature with crosspoint (in the old times of fido-net). Is it possible to color (in the index) a mail which is a reply to a mail from me? So that I can see very fast if someone answered

Re: Color mails which are a reply to a mail from me?

At 23:47 +0100 05 Jan 2002, Gerhard Siegesmund [EMAIL PROTECTED] wrote: I don't know if it is at all possible, but I loved this feature with crosspoint (in the old times of fido-net). Is it possible to color (in the index) a mail which is a reply to a mail from me? So that I can see very fast

Re: Color mails which are a reply to a mail from me?

I don't know if it is at all possible, but I loved this feature with crosspoint (in the old times of fido-net). Is it possible to color (in the index) a mail which is a reply to a mail from me? So that I can see very fast if someone answered me in a list? (Hope this is not a FAQ). - You

Re: Color mails which are a reply to a mail from me?

in message [EMAIL PROTECTED], wrote Aaron Schrab thusly... At 23:47 +0100 05 Jan 2002, Gerhard Siegesmund [EMAIL PROTECTED] wrote: I don't know if it is at all possible, but I loved this feature with crosspoint (in the old times of fido-net). Is it possible to color (in the index) a mail

Re: Color mails which are a reply to a mail from me?

also sprach Gerhard Siegesmund [EMAIL PROTECTED] [2002.01.05.2347 +0100]: I don't know if it is at all possible, but I loved this feature with crosspoint (in the old times of fido-net). Is it possible to color (in the index) a mail which is a reply to a mail from me? So that I can see very

Re: color problems after upgrade

I tried you colors, and those object where default is specified as the background, the aterm background shows thru - everything else - the message body, and the main index background is still white on black. perhaps your $TERM is xterm-color (except for hardcoded applications that ignore

Re: color problems after upgrade

On Tue, Dec 04, 2001 at 05:58:02AM -0500, Thomas Dickey wrote: I tried you colors, and those object where default is specified as the background, the aterm background shows thru - everything else - the message body, and the main index background is still white on black. perhaps your

Re: color problems after upgrade

On Tue, 4 Dec 2001, Dave Price wrote: On Tue, Dec 04, 2001 at 05:58:02AM -0500, Thomas Dickey wrote: I tried you colors, and those object where default is specified as the background, the aterm background shows thru - everything else - the message body, and the main index background is

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

Re: color problems after upgrade

William, On Mon, Dec 03, 2001 at 01:26:23PM -0800, Will Yardley wrote: what does your colors section look like? mine works fine, and i use the most recent release on both potato and woody with no problems. are you using 'default' for the background color? what TERM do you have set?

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

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

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

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

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

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

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

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

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

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

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

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

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.

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`. --

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

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

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

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;

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

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

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,

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

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

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

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

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

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

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

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

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

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

Re: Color Errors on Solaris

On Wed, May 23, 2001 at 05:11:39PM -0700, Igor Pruchanskiy wrote: mutt -v | grep System does it say [ncurses 4.2] or something like that ? if it does default should do, if you have no ncurses, i do not believe that it knows what default color is You can replace default with black or

  1   2   >