Hello,
what I mean is that (see original messages and excerpt from my
muttrc.vim below):
1) I received your reply
2) I selected it from the index
3) I saw your reply colored like this:
Headers : blue on grey
Your msg : Black on white
My original msg, now quoted: Black on grey
All as I want it to be. Now I have just hit "r" to reply, and see:
1) Headers above these lines in a mix of brightgreen, magenta and yellow
2) The "On 2001/04/25 18:52:50 -0400, Mr. Wade wrote:" line below black
on grey
3) Your reply (level one quoting) blue on grey
4) My orig. msg. (level 2 quoting) cyan on grey, practically unreadable
5) The text I'm writing now black on grey
Black on grey is the Xdefault I have set for all my xterms.
$EDITOR, $editor and $VISUAL are undefined.
The editor looks like some vi to me, from its behavior. I have done
find /usr /etc -type f -iname "*vi*"|grep -i mutt
and found /usr/share/vim/vim56/syntax/muttrc.vim
If I grep -i color on it, I get what follows below.
In short, I think your suggestions and comments do make a lot of sense,
but can't see in my setup anything related to them. I wonder if at this
point I should ask for some muttrc.vim file and compare against mine.
Any suggestion is appreciated.
rco Fioretti
FROM muttrc.vim
syn keyword muttrcCommand save-hook score send-hook source toggle unalias
uncolor unignore
syn keyword muttrcColorField contained attachment body bold error hdrdefault header
index
syn keyword muttrcColorField contained indicator markers message normal quoted
search signature
syn keyword muttrcColorField contained status tilde tree underline
syn match muttrcColorField contained "\<quoted\d\=\>"
syn keyword muttrcColorFG contained black blue cyan default green magenta red
white yellow
syn keyword muttrcColorFG contained brightblue brightcyan brightdefault
brightgreen
syn keyword muttrcColorFG contained brightmagenta brightred brightwhite
brightyellow
syn match muttrcColorFG contained "\<\(bright\)\=color\d\{1,2}\>"
syn keyword muttrcColorBG contained black blue cyan default green magenta red
white yellow
syn match muttrcColorBG contained "\<color\d\{1,2}\>"
syn keyword muttrcColor contained color skipwhite
nextgroup=muttrcColorField
syn match muttrcColorInit contained "^\s*color\s\+\S\+" skipwhite
nextgroup=muttrcColorFG contains=muttrcColor
syn match muttrcColorLine "^\s*color\s\+\S\+\s\+\S" skipwhite
nextgroup=muttrcColorBG contains=muttrcColorInit
" Mono are almost like color (ojects inherited from color)
syn keyword muttrcMono contained mono skipwhite
nextgroup=muttrcColorField
hi link muttrcColorField Identifier
hi link muttrcColorFG String
hi link muttrcColorBG muttrcColorFG
hi link muttrcColor muttrcCommand
hi link muttrcMonoAttrib muttrcColorFG
On 2001/04/25 18:52:50 -0400, Mr. Wade wrote:
> Marco Fioretti wrote:
> > I have colors set in .muttrc as I like both in the index and when
> > I read messages. When I *send* messages, however, i.e. whenever I
> > hit either the "r" or the "m" keys, mutt colors headers and quotes
> > in a different and unreadable way. I haven't found in the manual
> > or in the .muttrc files I downloaded from the net anything about
> > this, and even the /etc/Muttrc file doesn't contain anything related
> > to colors.
> >
> > I guess I could patch this with a send-hook which applies to ALL
> > outgoing messages, but I'd like to know both why does this happen,
> > and if there are more elegant/proper ways to do it.
> >
> > Any help/pointers/muttrc examples explaining how to set colors
> > only when sending messages would be really appreciated.
>
> If you are talking about the colors in your editor while you are
> composing the message, then Mutt is not responsible for coloring.
> You will need to address that issue with your editor's
> configuration files or settings.
>
> Note that the $editor variable specifies which editor is used by
> Mutt. It defaults to the value of the $EDITOR or $VISUAL
> environment variables, or to "vi". If $editor is null, then Mutt
> seems to use some sort of mailx-like internal editor (in which
> coloring is not an issue.)
>
> If you are talking about how message bodies look in the pager
> before sending, then I don't know how to help you. They are not
> colored the same way a message is colored when viewed in the
> pager, (but the headers are not displayed, so I am thinking you
> are talking about this, since you specifically mentioned the
> headers.) If readability is impaired, the object "normal" may
> help improve that, e.g.
>
> color normal cyan black
>
> I hope you get it fixed to your liking. :)
>
> -- Mr. Wade
>
> --
> Linux: The Choice of the GNU Generation
>
>
