hi freaks.
Is it possible to set the indicator foreground color to none?
I mark new, old mails with colors and so i don't want to let the
indicator change it.
TIA
marc(..)
On Feb 13, Marc Bruenink [[EMAIL PROTECTED]] wrote:
Is it possible to set the indicator foreground color to none?
I mark new, old mails with colors and so i don't want to let the
indicator change it.
Currently there isn't, but Mike Schiraldi has a patch which is also in the
CVS version
On Feb 13, Jeremy Blosser [[EMAIL PROTECTED]] wrote:
On Feb 13, Marc Bruenink [[EMAIL PROTECTED]] wrote:
Is it possible to set the indicator foreground color to none?
I mark new, old mails with colors and so i don't want to let the
indicator change it.
Currently there isn't, but Mike
Is it possible to set the indicator foreground color to none?
I mark new, old mails with colors and so i don't want to let the
indicator change it.
The latest CVS version of mutt makes the default indicator (i.e. mono
indicator reverse) simply the reverse of whatever color the message would
And I heard Mike Schiraldi exclaim:
just the background, but that sounds like a pretty good idea. We're working
on redesigning mutt's color system, but it's rather difficult to come up
with something that's simple in syntax yet powerful enough to do what you
requested. Plus (hopefully
Daniel Farnsworth Teichert wrote:
I imagine this has already been thought of, but one option would be to simply
let the mono attribute work on top of the color one. Then the desired behavior
from this original posting could be to set the mono to none, and not specify
the color attribute
On 09:41 13 Feb 2002, Michael Elkins [EMAIL PROTECTED] wrote:
| Daniel Farnsworth Teichert wrote:
| I imagine this has already been thought of, but one option would be to simply
| let the mono attribute work on top of the color one. Then the desired behavior
| from this original posting could
hi,
i tried...
#color index brightwhite default ~C $alternates
color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow))
...i get error message while starting mutt...
Error in /home/parv/cf/mail/mutt.cf, line 58: parentheses not balanced
...i don't see how above
On Feb 03, parv [[EMAIL PROTECTED]] wrote:
#color index brightwhite default ~C $alternates
color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow))
...i get error message while starting mutt...
Error in /home/parv/cf/mail/mutt.cf, line 58: parentheses
On Sun, Feb 03, 2002 at 03:38:18PM -0500, parv wrote:
hi,
i tried...
#color index brightwhite default ~C $alternates
color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow))
...i get error message while starting mutt...
Error in /home/parv/cf/mail
Jeremy Blosser wrote:
On Feb 03, parv [[EMAIL PROTECTED]] wrote:
#color index brightwhite default ~C $alternates
^^
Am I missing something? I believe the main goal of the original poster
is to achieve something like this...
color index
On Feb 03, Cedric Duval [[EMAIL PROTECTED]] wrote:
Jeremy Blosser wrote:
On Feb 03, parv [[EMAIL PROTECTED]] wrote:
#color index brightwhite default ~C $alternates
^^
Am I missing something? I believe the main goal of the original poster
i blurted...
color index brightwhite default ~C (parv_@yahoo\.com|parv@(localhost|.*holy\.cow))
...i get error message while starting mutt...
to which replied Benjamin Smith thusly (and Jeremy Blosser gave the
similar reply)...
Easily solved. This is due to mutt's weird parsing of its
On Jan 31, parv [[EMAIL PROTECTED]] wrote:
i am using mutt 1.3.27i, and i tried...
color indicator reverse
...which, of course, doesn't work as desired. what i want/wish is
to have indicator in reverse colors in the index. mono reverse is,
well, not colored.
possible?
Not currently
...which, of course, doesn't work as desired. what i want/wish is
to have indicator in reverse colors in the index. mono reverse is,
well, not colored.
I'm not 100% sure what you want, but if it's the following, try the latest
mutt out of CVS.
If the indicator bar is defined as mono
in message [EMAIL PROTECTED],
wrote Mike Schiraldi thusly...
...which, of course, doesn't work as desired. what i want/wish is
to have indicator in reverse colors in the index. mono reverse is,
well, not colored.
I'm not 100% sure what you want, but if it's the following, try the
as far as building from cvs goes, i will wait until that version is
released to the masses. it's a gushy gooey feeling that above
behaviour will be available from the mutt itself.
Well, you can always apply the attached patch to any recent version of
mutt. I'd post a URL, but it'd probably
i am using mutt 1.3.27i, and i tried...
color indicator reverse
...which, of course, doesn't work as desired. what i want/wish is
to have indicator in reverse colors in the index. mono reverse is,
well, not colored.
possible?
(yes i know the correct syntax is be color indicator fg bg
PROTECTED]' 100 # sent directly to me
set score_threshold_read=80 # mark potential spam as 'read'
no scoring required! :-)
tell mutt about your own addresses by
setting alternates - and then select
these by limiting to the pattern ~P.
you can use this pattern for colors, too:
color index red
How to make some different color in body something like
*text* _text_ etc?
--
-- [EMAIL PROTECTED] ===
| Debian GNU/Linux
_|_ ___ @AMD-K6-2
| O | | | http://home.macau.ctm.net/~toukp
Hi,
On Thu, Jan 24, 2002 at 07:12:11PM +0800, Pun Kuan Tou wrote:
How to make some different color in body something like
*text* _text_ etc?
It may have been done better before, but:
color body brightred default \\*[^*]{0,30}\\*
color body brightred default _[^_]{0,30
I solved my color problems with mutt-1.3.25. I did specify the curses
param incorrectly. It's fixed and I'm happily using the new mutt.
However, I have a different color issue to ask about. Under my new
compile of mutt with ncurses 5.2, I see yellow color as yellow (dtterm).
However, under my
On Thu, Jan 17, 2002 at 12:04:50PM -0800, Carl B. Constantine wrote:
I solved my color problems with mutt-1.3.25. I did specify the curses
param incorrectly. It's fixed and I'm happily using the new mutt.
However, I have a different color issue to ask about. Under my new
compile of mutt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thus spake Thomas Dickey ([EMAIL PROTECTED]):
When I ssh from my solaris 8 box to my home machine, color works
correctly (including yellow). However, when I ssh from my home
machine to my work-solaris 8 machine, mutt is in mono color though
On 12:04 17 Jan 2002, Carl B. Constantine [EMAIL PROTECTED] wrote:
| I solved my color problems with mutt-1.3.25. I did specify the curses
| param incorrectly. It's fixed and I'm happily using the new mutt.
|
| However, I have a different color issue to ask about. Under my new
| compile of mutt
Cameron Simpson wrote:
Colours are really just specified as slot numbers (1-8 standard,
another 8 in some more recent terminal emulators). So the actual hue
you get for a colour slot is a quality of implementation issue. My
Linux console shows my yellow prompt as an orange/brown too :-(
the same color model
--
Thomas E. Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
further to my last post, here's a sample of my .muttrc:
color signature brightred default
color tilde blue default
color tree brightmagenta default
color underline yellow default
color body yellow default [;:]-[)/(|] # colorise smileys
color body
and bottom is enough. (Refer to Vim's
modeline concept - for the majority of cases my name would only
appear at top or bottom of the message.)
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
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
[ 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
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
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
Hello Mailinglist
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
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
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
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
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
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
to set the
'folder browser' to follow my color commands. Any help?
I'm using the
folder_format=%N %C %F \ \ \ \ %f %\ %s
in my .muttrc
msg22210/pgp0.pgp
Description: PGP signature
Hi,
when I want to see only one part of a mime/multipart message with
the command view-attach (Enter), I cannot see the text colored. Is
there a way to enable it like in the pager?
Thanks,
Alberto
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
$TERM is xterm-color (except for hardcoded applications that
ignore $TERM, you won't see default colors working properly in that case).
it is rxvt in both cases - the difference, other than the mutt versions
is that one is running to a remote display (that one is good) and one is
local - the display
is still white on black.
perhaps your $TERM is xterm-color (except for hardcoded applications that
ignore $TERM, you won't see default colors working properly in that case).
it is rxvt in both cases - the difference, other than the mutt versions
is that one is running to a remote display
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
hi,
i just installed mutt 1.3.23i on a woody box ... previously, i was using
1.2.5i on a potato box via xterm (i want to run a local mutt with
fetchmail)
the first thin i notice is that 1.2.5 allows my xterm background to show
through (which i like) but the 1.2.23i seems to force the white on
Dave --
...and then Dave Price said...
% hi,
Hello!
%
% suggestions?
I'm sorry to say that I don't have any suggestions for your color
problems. Best of luck.
%
% also, any advice on copying my pgp key/user info over from the old box
% to the new one?
This should be as easy as tarring
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
On Thu, Nov 22, 2001 at 10:14:40PM -0500, Andy Wingo wrote:
Hi John,
On Thu, 22 Nov 2001, John Perry wrote:
Is
there some way to get Mutt to turn off it's colors and just give me black
on white?
No doubt more experienced users will chime in here, but the simple
solution is to say
background. The older 1.2.5 version of Mutt will let me get fairly
close to this goal. Under 1.3.23 all I can seem to get is white
characters on a black background, the exact opposite of what I'm looking
for. I've played with the color options until I'm blue in the face. Is
there some way to get Mutt
Hi John,
On Thu, 22 Nov 2001, John Perry wrote:
Is
there some way to get Mutt to turn off it's colors and just give me black
on white?
No doubt more experienced users will chime in here, but the simple
solution is to say
$ TERM=vt100 mutt
and now, await the correct solution in other
$ TERM=vt100 mutt
and now, await the correct solution in other responses ;)
peace,
Actually I found what I was looking for... It was the mono token. Now
I'm able to switch back and forth between color and B/W just by setting
the term type.
--
John Perry [EMAIL PROTECTED] PGP-encrypted e
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
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
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
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
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
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
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
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
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
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
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
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
* 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
.
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
* 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
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
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
On Mon Oct 22, 2001 at 06:00:59PM -0400, Thomas Dickey wrote:
On Mon, Oct 22, 2001 at 01:32:46PM +0100, Jonathan Perkin wrote:
Ok, so people might be getting bored with these colour problems, but
here's another one which is really starting to bug me and I'm hoping
someone can shed fresh
On Mon Oct 29, 2001 at 09:08:40AM -0500, Thomas E. Dickey wrote:
On Mon, 29 Oct 2001, Jonathan Perkin wrote:
Aye, actually had time to investigate this over the weekend and found
the offending stuff in mutt's configure script - for the use_default_color
checks it only includes curses.h
On Mon, 29 Oct 2001, Jonathan Perkin wrote:
Aye, actually had time to investigate this over the weekend and found
the offending stuff in mutt's configure script - for the use_default_color
checks it only includes curses.h - now on NetBSD this only exists in
/usr/include for system curses
Hi there,
I have 1.3.23i running on FreeBSD 4.4-STABLE (installed from the port),
and looks like I can't get color support. I had 1.2.5i on this box
(colors worked just fine), also installed from the port, deinstalled it,
and installed the 1.3.23i version. Same ~/.mutt/muttrc, which _is_ used
Date: Mon, 22 Oct 2001 11:32:18 +0200
From: Roman Neuhauser [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: no color in 1.3.23i
Hi there,
I have 1.3.23i running on FreeBSD 4.4-STABLE (installed from the port),
and looks like I can't get color support. I had 1.2.5i on this box
(colors
mail to [EMAIL PROTECTED].
To report a bug, please use the flea(1) utility.
-% mutt
Error in /home/sketch/.source/mutt/mutt.colour, line 38: default: no such color
[...]
source: errors in /home/sketch/.muttrc
Press any key to continue...
-% strings /usr/pkg/lib/libncurses.so.5.2|grep use_de
On Mon, Oct 22, 2001 at 01:32:46PM +0100, Jonathan Perkin wrote:
Ok, so people might be getting bored with these colour problems, but
here's another one which is really starting to bug me and I'm hoping
someone can shed fresh clues.. :)
there's no indication in the mutt -v, but you're
Lukas --
...and then Lukas Ruf said...
% Hi there,
Hello!
%
% for a couple of months I am using mutt, under Linux since it's been
...
%
% So the question: where can I define the color default
% such that the configuration of my muttrc:
% color normal default default # normal text
the following errors:
Error in /home/ruf/.mutt/muttrc, line 952: default: no such color
I followed the FAQ and, magically, there are some colors after that.
(I followed the points of Color doesn't work. All I get is a bold
(bright) font.)
So the question: where can I define the color default
Hi,
I just installed mutt-devel 1.3.22i (coming from 1.2.5i) and lost the
color display (everything is now BW)
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
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
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
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
* 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
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
* 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
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
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
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
* 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
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
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
...
* 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
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
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
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
All,
I apologize if this has been discussed and I missed it, but I recently
upgraded to 1.3.19i. When I did so, the default color seems to have
disappeared. I get about 20 of these errors:
Error in /home/nate/.muttrc, line 243: default: no such color
What should I replace this with? If I
On Thu, 9 Aug 2001, Nate Johnston wrote:
All,
I apologize if this has been discussed and I missed it, but I recently
upgraded to 1.3.19i. When I did so, the default color seems to have
disappeared. I get about 20 of these errors:
Error in /home/nate/.muttrc, line 243: default
Sorry if I am missing something basic here, but since I have been
playing with colors, something is different and I am not sure how. In
monochrome, I made the status bar bold. In color, it is brightcyan.
Yes, it's bright, but bold changes the text a bit in a way I really
liked, making the '-'s
I have been having rpoblems getting mutt 1.2.5 to color quoted text; my
quote_regexp is set to the default, my .muttrc does a 'reset all' at the
top, and I have the line color quoted blue black in my .muttrc as
well. However when running on a color terminal it does not work.
The strange thing
Lou,
I am happily repling to your message in the mutt editor, with properly
colored quotes and all, after replacing the mutt_vim_rc file with the
one you sent yesterday.
Thanks again!,
Marco
On 2001/07/10 20:18:20 -0400, Louis LeBlanc wrote:
I thought that file looked
301 - 400 of 624 matches
Mail list logo
