Re: colors like slrn? [screwup here]
You can always fish it up from the archives. Possibly you're using a white background, I have no idea what slrn would do under those conditions. Oh I kept the contents of the mail, just not in Mutt! I tried it again with a reverse video xterm and it works a lot better. You got the yellow slrn uses. It's just yellow but for some reason I didn't get it before. I'll figure the rest of it out from here. Thanks alot.
Re: colors like slrn?
On Wed, Jun 27, 2012 at 08:35:59AM -0700, ny6...@gmail.com wrote: I use a 256. Color scheme but it won't work on a term not set up for 256. I'm using xterm, I guess it would work. But are you saying your color scheme looks like slrn? Yea this list is kind of slow. :) I didn't mean slow, I meant it was kind of humorous seeing the Mutt.org mailing list page has links to click on that are for webmail clients! Mutt is so NOT about that!
Re: colors like slrn?
codeb...@inbox.lv wrote: I'm using xterm, I guess it would work. But are you saying your color scheme looks like slrn? At one time (a very long time ago) I had the configurations set up so that vim, mutt and slrn all had basically the same colour scheme. I have no idea if slrn still has the same colour scheme or even if I tweaked it at the time, since I haven't used it in so long, but here are my colour settings from .muttrc: color attachment yellow default color body brightred default [\-\.+_a-zA-Z0-9]+@[\-\.a-zA-Z0-9]+ color body brightblue default (http|ftp)://[\-\.\,/%~_:?\#a-zA-Z0-9]+ color bold brightwhite default color error red default color header yellow default ^Subject: color header yellow default ^From: color header yellow default ^Date: color header yellow default ^To: color header yellow default ^Cc: color header yellow default ^Reply-To: color hdrdefault cyan default color index white default \.* color indicator brightyellow red color markers magenta default color message white default color normal white default color quoted green default color search red yellow color signature blue default color status brightyellow blue color tilde magenta default color tree red default color underline magenta default
Re: colors like slrn? [screwup here]
codeb...@inbox.lv wrote: I think it was Chris who just sent his color file? I'm sorry, I deleted the message accidentally. I tried it and the colors work really bad on my terminal for some reason. I couldn't see anything which is why I deleted your message accidentally :-/ Anyway thanks for sending it. At least we tried! You can always fish it up from the archives. Possibly you're using a white background, I have no idea what slrn would do under those conditions.
Re: colors like slrn? [screwup here]
On Wed, Jun 27, 2012 at 05:43:24PM +0100, Chris Burdess wrote: codeb...@inbox.lv wrote: I think it was Chris who just sent his color file? I'm sorry, I deleted the message accidentally. I tried it and the colors work really bad on my terminal for some reason. I couldn't see anything which is why I deleted your message accidentally :-/ Anyway thanks for sending it. At least we tried! You can always fish it up from the archives. Possibly you're using a white background, I have no idea what slrn would do under those conditions. I'll try on a reverse video terminal later and get back to you. Thanks.
Re: Colors, mutt, termcap/terminfo
On Tue, Jun 08, 2010 at 05:17:06PM -0700, Chip Camden wrote: I finally got 256 colors working with mutt and zsh on FreeBSD. Even though both of Look for the 256colors2.pl perl color test script. It will help you verify 256 colors is *really* working. Many times I thought I had 256 colors, but until I tested the terminal using this script, I didn't know for sure. Also, VIM gets really finicky with 256 colors enabled when switching between virtual terminal and Xorg. On virtual terminals, colors are negated within the kernel level code, which still doesn't do 256 color term. However, framebuffer has tons of colors, but still doesn't support 256 terminal colors ... again, it's kernel level code that apparently needs fixing. (?) -- Roger http://rogerx.freeshell.org/
Re: Colors, mutt, termcap/terminfo
[Re: Colors, mutt, termcap/terminfo] rog...@sdf.org schrieb am 09.06.2010 um 00:01 (-0800): On Tue, Jun 08, 2010 at 05:17:06PM -0700, Chip Camden wrote: I finally got 256 colors working with mutt and zsh on FreeBSD. Even though both of Look for the 256colors2.pl perl color test script. It will help you verify 256 colors is *really* working. http://code.google.com/p/joeldotfiles/source/browse/trunk/256colors2.pl Fantastic! Works great on rxvt and MinTTY on Cygwin. I didn't know the terminal could be so colorful, used to think it was limited to 256 colors. -- Michael Ludwig
Re: Colors, mutt, termcap/terminfo
On Wed, Jun 09, 2010 at 04:48:58PM +0200, Michael Ludwig wrote: Michael Ludwig schrieb am 09.06.2010 um 16:09 (+0200): http://code.google.com/p/joeldotfiles/source/browse/trunk/256colors2.pl Fantastic! Works great on rxvt and MinTTY on Cygwin. I didn't know the terminal could be so colorful, used to think it was limited to 256 colors. And there are colors beyond 255, but it looks like they repeat: $ perl @c = map sprintf( \x1b[48;5;%um%4u, $_, $_), 0 .. 1023; print @r\n while @r = splice @c, 0, 32; 16 bit + does have more colors ;-) ... but for some reason, terminals only have been defined a limited few. ... and like I already mentioned, the virtual terminals (the default linux terminal) don't know how to even use these colors due to kernel code. Here's the post stating the specifics limitations. TTY with 256 colors? http://superuser.com/questions/67582/tty-with-256-colors If you want 256 color support on virtual terminals you'll have to build you own kernel after extending the code that parses the escape sequences to handle the wider color-specification. This is why I'm avoiding 256 colors for now, because I use both virtual and Xorg terminals, and if applications are defined to use 256, they (VIM) tend to screw their colors on any default color spec display (ie. linux virtual terminals). Enjoy 256 color if you can! Code seems to be more easily read with the extended colors in VIM/GVIM. ;-) -- Roger http://rogerx.freeshell.org/
Re: Colors suddenly died
On 02-06-2010 13:58, Chip Camden wrote: Hello mutt-users, I'm not sure how or when, but I suddenly lost most colors in mutt. If I change the normal color, that shows up, but others like attachment and hdrdefault no longer seem to work. I'm on a FreeBSD system following their 8.1-PRERELEASE, so it probably has to do with updating something, but I have no idea what. vim still colors corrrectly, as does everything else I've tried. I've rebuilt ncurses and mutt, no help. This coloring fails both in and out of X. The line-drawing characters have also changed -- now I'm seeing ^@ for the L line, for instance. Anyone seen something like this before? Yes. I noticed the same thing a while ago (also on FreeBSD). I think I solved it by removing the ncurses port (not sure why I had it installed in the first place, ncurses is in base) and rebuilding mutt. -- Joel
Re: Colors suddenly died
On Jun 03 2010 08:18, Joel Dahl wrote: On 02-06-2010 13:58, Chip Camden wrote: Hello mutt-users, I'm not sure how or when, but I suddenly lost most colors in mutt. If I change the normal color, that shows up, but others like attachment and hdrdefault no longer seem to work. I'm on a FreeBSD system following their 8.1-PRERELEASE, so it probably has to do with updating something, but I have no idea what. vim still colors corrrectly, as does everything else I've tried. I've rebuilt ncurses and mutt, no help. This coloring fails both in and out of X. The line-drawing characters have also changed -- now I'm seeing ^@ for the L line, for instance. Anyone seen something like this before? Yes. I noticed the same thing a while ago (also on FreeBSD). I think I solved it by removing the ncurses port (not sure why I had it installed in the first place, ncurses is in base) and rebuilding mutt. -- Joel That did the trick! Thanks, Joe1! I guess that means that mutt isn't compatible with the development version of ncurses? -- Sterling (Chip) Camden | camdensoftware.com | chipstips.com | chipsquips.com
Re: Colors in quoted *replies*
Le 19-08-2009, à 09:13:04 -0500, Kyle Wheeler (kyle-m...@memoryhole.net) a écrit : Lignes : 38 On Wednesday, August 19 at 03:59 PM, quoth steve: (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) vim too. Well then, it's simply a matter of adding the following line to your ~/.vimrc: syntax on Well that's done since ages but doesn't help here, all quoted lines are in the same color. steve
Re: Colors in quoted *replies*
Le jeudi 20 août de l'année 2009, vers 10 heures et 17 minutes, steve écrivait: Well that's done since ages but doesn't help here, all quoted lines are in the same color. Salut Steve, and with colorsheme option in vimrc ? -- Alexandre Delanoë
Re: Colors in quoted *replies*
On Thu, 20 Aug 2009, steve wrote: Well that's done since ages but doesn't help here, all quoted lines are in the same color. When replying the temp file is /tmp/mutt-xx and filetype.vim inside vim should be able to detect it's filetype as 'mail'. try verify :set ft? or :set syn? or examine the scripts loaded by :scriptnames to see if mail.vim is loaded or overrided. -- regards, GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
Re: Colors in quoted *replies*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, August 19 at 03:49 PM, quoth steve: I have colors when I read a message, but not when I'm replying to it. How can I get this? Get a better text editor (or learn how to use the one you've got). (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) ~Kyle - -- Nothing makes a woman more beautiful than the belief she is beautiful. -- Sophia Loren -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjAP0AAoJECuveozR/AWeX6cP+gJxaiMQ24OiFMfFK/PB+k/B +MjxMfbpj5QGG/VbQmp+0HT+eP4k0ebqtXnuchtEUqMR1WmirwGTG8QIq96bcFKN iwlaEtTn6ZhYbRvL50i+X4f5IduqgSGeh5vzeJZhqpSlwDZxAsTGvlHS65Vo0WwN DmEnKewmXK/+tFIylfsWsm9JExvUO2SxAVc5417HxbFfbFSQcQhi7bxH7maTDiOH lCSMXBhhqVZ8oRhUo9P2ZmXfkyIpumSZY5aUfcWhJ5JyWQ5MI7+oPiPbytLN/9eX rWwqRT1mhyhd/MFtIUuSwRz/GCEFEtBA/67HcgXWkmHy5AxAlC1VBJm0TOAZVZft b2/1XSym//jXKwqofYrEJRRCH6DFE/5KcYzazkKPglTPGzQR3657rPtrM3qHkHp2 rhPeUP5c9kDEmxzUHKERP/kJB2nPGwuucJWXKgSYnlzrOnM+pDAiWF7Ux3VaKCFP jPXSX6Rzxzo1lBbh+fNz1AqqBT/j2PZJw6KXMA2Cv6oXZy2QKT2isU4Pho6pJvfU dDiEx85QQyLTl8E4Ymz94mn+Fc/5QwRDZ4jOkbvHZ+Oxt5b7qppdkLdSmprtvaX0 MAaqKOCCTjyNghl6UtQv3agFyCkUOJ0OVTfFOJ6NeCdBZGA3errmj8PkxTCyvg+4 V1fur+neyXpJx31oNl7j =a+Ok -END PGP SIGNATURE-
Re: Colors in quoted *replies*
Le 19-08-2009, à 08:53:56 -0500, Kyle Wheeler (kyle-m...@memoryhole.net) a écrit : On Wednesday, August 19 at 03:49 PM, quoth steve: I have colors when I read a message, but not when I'm replying to it. How can I get this? Get a better text editor (or learn how to use the one you've got). I just realized that when replying it's the editor which is displaing the text, not mutt... (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) vim too. Thanks steve
Re: Colors in quoted *replies*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, August 19 at 03:59 PM, quoth steve: (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) vim too. Well then, it's simply a matter of adding the following line to your ~/.vimrc: syntax on ~Kyle - -- Men think epilepsy divine, merely because they do not understand it. But if they called everything divine which they do not understand, why, there would be no end of divine things. -- Hippocrates -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjAhwAAoJECuveozR/AWeae4P/3c06iVNKp8lNNK3NraraaOK A5OQcMxcyQN476Bb30zvMH1gsL4XgTKztvOSRj6q6VG/ImJfAa21QF14Q71rO4Yz OLSNoV1XxkL+hrH0q21+aBUW1Fu98NBDnW3OjIFMW4RG8sqxkM1H1iwJhl6JLD66 sS7YM+4M5VdZ42K9hGFxm+CsslCzqZXSyH8V8C6kUyV2k3WdSEKh7tPXfuOVOI8T O5OT4OJCvbj8KhEIVXRxLD0uAzsm7iMzi2DNBg6CKi+ZSUQg0OsGwsexE7kRk3Nq 9EOFjBfUrFDH61+I4gFS+SHDSVKi4ooxYlZEu0jYJUgh4sAiDfnDB/BCqH+mowy+ 7xqvC0Qj9wAU0UYaOrEu2At8in5hZsopYvffQxQc3BRR0xRuAc9qY/G+RKOmvSxW zmCSKSKLSAow1xKmeAPj/YmY5f8M0iWIx1vSAl88S+dild08eVMQ2fRslM77pR5m lHidykVJU3paFUdfy5REz90piTb2msPbZQav3h4VhSP6PdGol7Y6aM0duUOJmopy /RrdXDkOItoZ/zUTAWEIkep4l572TsVgv/aKk7oa7E3VookmR6O6m/fwCDCaZDyk thTmtMNXYkNdTE1hZ2QhmiRO5ZHaVkiTQtP1zSuyMkSszNze0U9PvW2JNxKmm0EV pOk/V+eFAa3XE+fYILR1 =HNjT -END PGP SIGNATURE-
Re: colors
Hi, * Jan-Herbert Damm wrote: My Ubuntu-custom version of Mutt-1.18. uses a different coloring scheme than the latest snapshot that i am testing now. In both cases i can't figure out where these default colors are being defined. /etc/Muttrc doesn't elaborate it and neither does my .muttrc. The Manual describes how to set colors but AFAIK not where the defaults are being defined. By default, mutt does not have default colors, it runs in mono. To verify: mutt -nF /dev/null I'd say it'd be really strange if neither /etc/Muttrc nor .muttrc contained color statements _and_ you get colors. But remember that it uses the Muttrc from its prefix which is likely not /etc/Muttrc for custom builds. E.g. I install in ~/opt/mutt so my system muttrc is not /etc/Muttrc but ~/opt/mutt/etc/Muttrc. HTH, Rocco
Re: colors
Rocco Rutte wrote on 27.06.09: * Jan-Herbert Damm wrote: My Ubuntu-custom version of Mutt-1.18. uses a [...] coloring scheme Where are these default colors being defined? I'd say it'd be really strange if neither /etc/Muttrc nor .muttrc contained color statements _and_ you get colors. Sorry, I oversaw the very last line in /etc/Muttrc. It sources /usr/lib/mutt/source-muttrc.d which again invokes the sourcing of /etc/Muttrc.d/* which contains a file covering nothing but the colors. I guess that is ubuntu/debian style. And yes my home-built Mutt-1.20. is mono. jan
Re: colors
On Sat, Jun 27, 2009 at 06:46:12PM +0200, Jan-Herbert Damm wrote: Rocco Rutte wrote on 27.06.09: * Jan-Herbert Damm wrote: My Ubuntu-custom version of Mutt-1.18. uses a [...] coloring scheme Where are these default colors being defined? I'd say it'd be really strange if neither /etc/Muttrc nor .muttrc contained color statements _and_ you get colors. Sorry, I oversaw the very last line in /etc/Muttrc. It sources /usr/lib/mutt/source-muttrc.d which again invokes the sourcing of /etc/Muttrc.d/* which contains a file covering nothing but the colors. I guess that is ubuntu/debian style. And yes my home-built Mutt-1.20. is mono. jan I have only recently started using the standard Ubuntu mutt as I have only recently started using Ubuntu. So, thanks for that. I had not realsied that Ubunta does it that way. In fact I had not looked at any of the ssytem muttrcs. I had just updated and tuned my old ones that have evolved over more than a decade. Another color question - where is the default color defined? My muttrc uses default for the background all the time and it is obviously white as I prefer, but I do not see it defined. The Ubuntu muttrcs do not use default, but define the background as black. Brian. -- Microsoft is not the answer. It is the question. The answer is 'No'. -- Unknown Brian Salter-Duke (Brian Duke) Email: b_duke(AT)bigpond(DOT)net(DOT)au
Re: colors
* On Sun, Jun 28, 2009 08:47AM +1000 Brian Salter-Duke (b_d...@bigpond.net.au) muttered: Another color question - where is the default color defined? My muttrc uses default for the background all the time and it is obviously white as I prefer, but I do not see it defined. The Ubuntu muttrcs do not use default, but define the background as black. http://www.mutt.org/doc/devel/manual.html#color | If your terminal supports it, the special keyword default can be used | as a transparent color. HTH, Michael -- I've run DOOM more in the last few days than I have the last few months. I just love debugging ;-) (Linus Torvalds) PGP-Key-ID: 0xDC1A44DD Jabber: init...@amessage.de
Re: colors
On Sun, Jun 28, 2009 at 01:36:01AM +0200, Michael Tatge wrote: * On Sun, Jun 28, 2009 08:47AM +1000 Brian Salter-Duke (b_d...@bigpond.net.au) muttered: Another color question - where is the default color defined? My muttrc uses default for the background all the time and it is obviously white as I prefer, but I do not see it defined. The Ubuntu muttrcs do not use default, but define the background as black. http://www.mutt.org/doc/devel/manual.html#color | If your terminal supports it, the special keyword default can be used | as a transparent color. So it is terminal thing. I had always thought it was a mutt thing. I must read the manual more often. Thanks, Michael. Brian. HTH, Michael -- I've run DOOM more in the last few days than I have the last few months. I just love debugging ;-) (Linus Torvalds) PGP-Key-ID: 0xDC1A44DD Jabber: init...@amessage.de -- Faith is the great cop-out, the great excuse to evade the need to think and evaluate evidence. Faith is belief inspite of, even perhaps because of, the lack of evidence. -- Richard Dawkins Brian Salter-Duke (Brian Duke) Email: b_duke(AT)bigpond(DOT)net(DOT)au
Re: Colors vanish when I open email from attachments menu..
=- Dilip M wrote on Tue 8.Jan'08 at 18:10:31 +0530 -= When I open the email from attachment menu, the colors of message, quoted text, doesn't show up. How to get this work? Please suggest.. Go back to normal pager mode with quit. Attachment mode is not meant for this flashy stuff. -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 06:31:12PM -0700, [EMAIL PROTECTED] wrote: The way I see it is... if I could get rid of these bright white characters over deep black background that bother my eyes so much whenever getting a nano screen to compose a message within mutt, thus making my experience with mutt so much more pleasant for the next few months (before switching to vim) - and it should take a couple of minutes to make such change when someone who has done it tells me how - then it's well worth doing. Just put: set editor=/usr/bin/vim in your .muttrc Personalise your colours for vim in your .vimrc (Obviously, this is the wrong mailing list for discussions on vim as would discussions on mutt be on a vim mailing list.) And secondly, just for the sake of being capable of doing so... Isn't this what being a linux user and a mutt user is all about? :) Not quite all, :-). Helps avoid malware. -- Chris. ==
Re: Colors and... nano or native pager??
On Mon, Sep 17, 2007 at 07:42:55AM -0700, [EMAIL PROTECTED] wrote: OK, this is what I found out from experimentation and further inquiry... What I initially wanted to achieve with nano (that is, to make the whole screen background white while in console - the same as with mutt) is impossible: nano allows only for color *highlighting*, and that's all. The color background feature works only in the context of *syntax highlighting*, which is what I did not quite grasp at first. For background colors in the console: man setterm -- Chris. ==
Re: Colors and... nano or native pager??
On Mon, Sep 24, 2007 at 10:23:48AM -0400, Chris Bannister wrote: Just put: set editor=/usr/bin/vim in your .muttrc Personalise your colours for vim in your .vimrc (Obviously, this is the wrong mailing list for discussions on vim as would discussions on mutt be on a vim mailing list.) Well, I can do that now, having dropped nano and installed vim, following the advice I got here at the time... You are right, this is probably not the right place to discuss vim. Franz pgpdPVS3IsgKJ.pgp Description: PGP signature
Re: Colors and... nano or native pager??
--- cga2000 [EMAIL PROTECTED] schrieb: (1) http://www.viemu.com/a_vi_vim_graphical_cheat_sheet_tutorial.html (2) http://www.cs.cmu.edu/~maverick/VimColorSchemeTest/ Thanks!!! Franz Die etwas anderen Infos rund um das Thema Reisen. BE A BETTER WELTENBUMMLER! www.yahoo.de/clever
Re: Colors and... nano or native pager??
Hallo Franz, So, are you a lot of you guys using external textmode editors in the place of Mutt's primitive one? What are the intelligent Yes, I use joe. alternatives? Is it feasible, then, to make your external textmode editor match mutt's colors? I went the other way round and configured mutt to match the color settings coming with joe: http://www.lespocky.de/lheismut.htm#mutt (the color config is almost at the bottom of the screen in section Farben in mutt) Greets Alex -- * http://www.lespocky.de *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 pgpGCOC9BqDj9.pgp Description: PGP signature
Re: Colors and... nano or native pager??
* Alexander Dahl [EMAIL PROTECTED] wrote: So, are you a lot of you guys using external textmode editors in the place of Mutt's primitive one? What are the intelligent Yes, I use joe. Me too, but I didn't adapt the color config. It's an editor, not a painter ;p -- left blank, right bald pgpnYvYWpevs0.pgp Description: PGP signature
Re: Colors and... nano or native pager??
OK, this is what I found out from experimentation and further inquiry... What I initially wanted to achieve with nano (that is, to make the whole screen background white while in console - the same as with mutt) is impossible: nano allows only for color *highlighting*, and that's all. The color background feature works only in the context of *syntax highlighting*, which is what I did not quite grasp at first. Of course, you can have the whole background white (or any other color) when nanoing within an X terminal... As far as making nano exhibit the same color patterns as mutt (when in an X terminal), here is the syntax of a rudimentary mutt colors .nanorc configuration I made:: ### # MUTT COLORS # ### syntax default color black,white . color blue,white ^From:.* color blue,white ^To:.* color blue,white ^Date:.* color blue,white ^Reply-To:.* color blue,white ^Cc:.* color blue,white ^Bcc:.* color red,white ^Subject:.* color blue,white ^X-Spam-Status:.* color blue,white (https?|ftp)://[\-\.,/%~_:?=3D\#a-zA-Z0-9]+.* color blue,white ^.* color magenta,white ^ .* color red,white ^ .* color green,white ^ .* color black,cyan ^gpg: Signature made.* color black,green ^gpg: Good signature from +.* color black,yellow^gpg: Can't check signature +.* color black,yellow^gpg: WARNING: .* color white,red ^gpg: BAD signature from.* END OF MUTT COLORS ## I am posting this information should someone following this thread find it useful. Franz
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 11:03:05AM -0700, Gary Johnson wrote: I don't know what you mean by mutt's editor/pager. Mutt uses: o a line editor for editing the command line, which is built-in; o a pager, which can be built-in or external; o a line editor for editing messages in mailx mode, which is built-in; o a text editor for editing messages in any other mode, which is external. What if editor=builtin? Is that what you mean by mailx mode? -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you.
Re: Colors and... nano or native pager??
On 2007-09-17, A Darren Dunham [EMAIL PROTECTED] wrote:
On Sun, Sep 16, 2007 at 11:03:05AM -0700, Gary Johnson wrote:
I don't know what you mean by mutt's editor/pager. Mutt uses:
o a line editor for editing the command line, which is built-in;
o a pager, which can be built-in or external;
o a line editor for editing messages in mailx mode, which is
built-in;
o a text editor for editing messages in any other mode, which is
external.
What if editor=builtin? Is that what you mean by mailx mode?
What I meant by mailx mode is this from the man page:
OPTIONS
...
-x Emulate the mailx compose mode.
That is the only way I've ever seen mutt use its built-in editor for
editing messages.
Before I wrote that reply I checked to see if setting 'editor' to
builtin would really work. I tested it by trying to edit ('e') a
message, which failed because mutt tried to invoke builtin as an
external command. That was not the smartest test I could have run.
I concluded that setting 'editor' to builtin did not work.
Just now I set 'editor' to builtin again to verify my earlier
results, but tested it by replying to a message. It worked! So I
stand corrected: Mutt does have an internal editor that can be
invoked from the normal UI.
Thanks, Darren, for asking the question. I learned something new
about mutt. I apologize for leading anyone astray with my earlier
reply.
Regards,
Gary
Re: Colors and... nano or native pager??
=- [EMAIL PROTECTED] wrote on Sun 16.Sep'07 at 6:30:04 -0700 -=
{ color config }
I do not know enough to create my own, so can someone suggest
where some good code to that extent for my .muttrc can be found?
See ConfigList on wiki.
Advantages/disadvantages of using an external editor?
External editor (which need not be GUI like nano!) is always better
than mutt's built-in (if you really meant that rather than merely a
_textmode_ editor like vi), because built-in is too primitive to be
happy with it all the time.
Then you choose between GUI (nano) and TUI (vi or the like).
GUI needs X, which you sometimes don't have when you use mutt, so a
TUI would be better to get used to if you expect non-X setups.
As for pager: stick with mutt's as long as possible, it's powerful
enough.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
Re: Colors and... nano or native pager??
On (16/09/07 06:30), [EMAIL PROTECTED] wrote:
...
I use it from console most of the time and tried a couple of color
combinations, but the bright colors coupled with the traditional
black background get to fatigue my eyes very quickly.
My preference would be a white/light gray background and not-too-
bright colors that are easy on the eyes.
I do not know enough to create my own, so can someone suggest
where some good code to that extent for my .muttrc can be found?
...
Here's one way of doing it, mostly lifted from the efforts of
others. You can fiddle with colors to suit yourself, of course.
## MUTT COLORS
# valid colors : white, black, green, magenta,
#blue, cyan, yellow, red,
# Each color comes in plain (red) and bright (brightred)
# color thisthing foreground background [arguments]
color normalblack default
color attachment black cyan
color hdrdefault cyan white
color indicator black green
color markers red white
color index green default ~N # New
color index magenta yellow ~T # Tagged
color index black white ~D # Deleted
color index blue default ~O# Old
color index red default '~f cron'
color index red default '~f Anacron'
color index brightyellow black ~b '\ name.{0,9}\=.{2,30}\.zip'
color index red yellow '~f root'
color quoted blue white
color quoted1 green white
color quoted2 magenta white
color quoted3 yellow white
color signature red cyan
color status yellow blue
color tilde blue white
color tree red white
color header blue white ^From:
color header blue white ^To:
color header blue white ^Date:
color header blue white ^Reply-To:
color header blue white ^Cc:
color header red white ^Subject:
color header blue white ^X-Spam-Status:
color body red white [EMAIL PROTECTED]
color body blue white (https?|ftp)://[\-\.,/%~_:?=\#a-zA-Z0-9]+
# Errors will be printed in red:
color error brightred brightdefault
Additionally, if you are deploying gpg, you can color the messages thus:
# GPG/PGP related color directives:
mono bodybold^gpg: Good signature
mono bodyreverse ^gpg: Bad signature from.*
color bodybrightblack cyan ^gpg: Signature made.*
color bodybrightblack green ^gpg: Good signature from.*
color bodybrightblack yellow^gpg: Can't check signature
.*
color bodybrightblack yellow^gpg: WARNING: .*
color bodybrightwhite red ^gpg: BAD signature from.*
HTH
--
[EMAIL PROTECTED]
GPG key 1024D/99421A63 2005-01-05
EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63
gpg --keyserver subkeys.pgp.net --recv-keys 99421A63
signature.asc
Description: Digital signature
Re: Colors and... nano or native pager??
On 2007-09-16, [EMAIL PROTECTED] wrote: I use it from console most of the time and tried a couple of color combinations, but the bright colors coupled with the traditional black background get to fatigue my eyes very quickly. My preference would be a white/light gray background and not-too- bright colors that are easy on the eyes. I do not know enough to create my own, so can someone suggest where some good code to that extent for my .muttrc can be found? The color settings in your .muttrc allow you to choose from the palette provided by your terminal program. That is, for example, you can choose the terminal's red, the terminal's blue or the terminal's brightred, but if you want a different shade of red you'll have to change the color(s) used by the terminal and that is typically done in ~/.Xdefaults, if you're using an X terminal. Also, I am debating whether to keep nano as editor (which makes it much easier for me at this time) or force myself to revert to the editor/pager that comes with Mutt and force myself to use that instead from the very start... Advantages/disadvantages of using an external editor? I don't know what you mean by mutt's editor/pager. Mutt uses: o a line editor for editing the command line, which is built-in; o a pager, which can be built-in or external; o a line editor for editing messages in mailx mode, which is built-in; o a text editor for editing messages in any other mode, which is external. Other than when in mailx mode, and I doubt you're using that, mutt has no internal text editor. It always uses an external editor for editing messages and defaults to using $EDITOR, $VISUAL or vi. So your choices are nano or some other external editor. If you're happy using nano, keep using it. I'd recommend using mutt's internal pager. It has all the features you need for reading e-mail and you can execute mutt commands while in the pager, which you can't do from an external pager. HTH, Gary
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 03:44:42PM +0200, Rado S wrote: External editor (which need not be GUI like nano!) is always better than mutt's built-in (if you really meant that rather than merely a _textmode_ editor like vi), because built-in is too primitive to be happy with it all the time. Then you choose between GUI (nano) and TUI (vi or the like). GUI needs X, which you sometimes don't have when you use mutt, so a TUI would be better to get used to if you expect non-X setups. As for pager: stick with mutt's as long as possible, it's powerful enough. Actually nano is a tiny textmode console editor, very much like pico and vi, and does not need X. So, are you a lot of you guys using external textmode editors in the place of Mutt's primitive one? What are the intelligent alternatives? Is it feasible, then, to make your external textmode editor match mutt's colors? Franz
Re: Colors and... nano or native pager??
On 2007-09-16, [EMAIL PROTECTED] wrote: On Sun, Sep 16, 2007 at 11:03:05AM -0700, Gary Johnson wrote: HTH, Gary HTH, Franz (what's HTH?) Hope That Helps or Hope This Helps. Regards, Gary
Re: Colors and... nano or native pager??
On (16/09/07 12:28), [EMAIL PROTECTED] wrote: ... So, are you a lot of you guys using external textmode editors in the place of Mutt's primitive one? What are the intelligent alternatives? Is it feasible, then, to make your external textmode editor match mutt's colors? I flinch at the thought of the flame-wars that may result from this simple factual statement: my .muttrc reads # set my choice for editor set editor=/usr/bin/emacs-snapshot -geometry 75x39 Substitute the emacs or other editor of your choice. By the way, emacs-snapshot is available by adding to your /etc/apt/sources.list: deb http://emacs.orebokech.com sid main -- [EMAIL PROTECTED] GPG key 1024D/99421A63 2005-01-05 EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 signature.asc Description: Digital signature
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 03:21:29PM EDT, [EMAIL PROTECTED] wrote: On Sun, Sep 16, 2007 at 11:25:05AM -0400, John wrote: Here's one way of doing it, mostly lifted from the efforts of others. You can fiddle with colors to suit yourself, of course. Thank you so very much, John. Actually, right after looking at your code I started fiddling with it as suggested, and I came up with something quite satisfactory to my taste. The only thing, at this line: color normalblack default I had to change default to white in order to get a white background. Also changed a few others things... and this totally takes care of my first question. Thanks again! It's been very much appreciated. As to the other question, mutt's vs. an external text editor, if I were to keep nano for the time being, how would I go about making nano display the same color pattern I have already achieved in mutt? Dunno about nano but you certainly could do it with vim. http://www.geocities.com/fcky1000/fcky/pager.png http://www.geocities.com/fcky1000/fcky/editor.png Time to switch?
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 01:14:59PM -0700, Gary Johnson wrote: On 2007-09-16, [EMAIL PROTECTED] wrote: (what's HTH?) Hope That Helps or Hope This Helps. Yes, very much, thanks. You guys have been very much helpful... What I still would like to know is, do I have to accept using nano (as Mutt's email editor) in black white, or is it possible to make nano display the same colors (as mutt displays based on the .muttrc configuration file?) I built nano 2.0.6 configured with color and .nanorc (the nano configuration file) enabled. Can some of you who are using the nano editor with colors kindly let me know how to do it, or where to learn more about it? The nano manual and instructions for the .nanorc don't seem to help at all... Franz
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 06:16:31PM -0400, John wrote: I flinch at the thought of the flame-wars that may result from this simple factual statement: my .muttrc reads # set my choice for editor set editor=/usr/bin/emacs-snapshot -geometry 75x39 Substitute the emacs or other editor of your choice. By the way, emacs-snapshot is available by adding to your /etc/apt/sources.list: deb http://emacs.orebokech.com sid main Using nano (a tiny 100 KB editor), the color configuration needs to be done in the .nanorc config file in the home directory. It features complex regex rules (at least to me, that is)... I don't think nano would be capable of using what you pointed out... then, again, I might be wrong. There's got to be someone here who is an expert on mutt and nano... Franz
Re: Colors and... nano or native pager??
On 16.09.2007 (15:36), [EMAIL PROTECTED] wrote: What I still would like to know is, do I have to accept using nano (as Mutt's email editor) in black white, or is it possible to make nano display the same colors (as mutt displays based on the .muttrc configuration file?) Is this perhaps the place to suggest a switch to vim...? Not only is it the best editor in existence, it also has any color scheme imaginable (and then some). For nano, you could google nanorc. At dotfiles, there are some. I don't know how they work, though. Try them out: http://www.dotfiles.com/index.php?cat_id=9 -- Our timetable will achieve the stature of a natural phenomenon. A planet's life is a vast, tightly interwoven fabric. Vegetation and animal changes will be determined at first by the raw physical forces we manipulate. As they establish themselves, though, our changes will become controlling influences in their own right -- and we will have to deal with them, too. Keep in mind, though, that we need control only three percent of the energy surface -- only three percent -- to tip the entire structure over into our self-sustaining system. -- PARDOT KYNES, Arrakis Dreams
Re: Colors and... nano or native pager??
On Mon, Sep 17, 2007 at 12:59:26AM +0200, Eyolf ?strem wrote: Is this perhaps the place to suggest a switch to vim...? Not only is it the best editor in existence, it also has any color scheme imaginable (and then some). For nano, you could google nanorc. At dotfiles, there are some. I don't know how they work, though. Try them out: http://www.dotfiles.com/index.php?cat_id=9 Learning vim, as I just said in my previous message, is one of my future plans... At this time I would like to concentrate on learning mutt, and doing it well. Those .nanorc files on the web basically deviate very little to not at all from the .nanorc included with the nano distribution. The only reference to mutt (email) colors I was able to find so far is: syntax mutt color green .* That's all... There must be someone here who has used nano with mutt... and hopefully they'll read this thread sooner or later... Franz
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 07:19:11PM EDT, [EMAIL PROTECTED] wrote: On Mon, Sep 17, 2007 at 12:59:26AM +0200, Eyolf ?strem wrote: Is this perhaps the place to suggest a switch to vim...? Not only is it the best editor in existence, it also has any color scheme imaginable (and then some). For nano, you could google nanorc. At dotfiles, there are some. I don't know how they work, though. Try them out: http://www.dotfiles.com/index.php?cat_id=9 Learning vim, as I just said in my previous message, is one of my future plans... At this time I would like to concentrate on learning mutt, and doing it well. If you plan to switch to vim at some point in the future, why would you want to bother about such trivial aspects as nano coloring? Don't waste time fine-tuning a car that's headed for the junkyard.
Re: Colors and... nano or native pager??
On Sun, Sep 16, 2007 at 09:15:12PM -0400, cga2000 wrote: If you plan to switch to vim at some point in the future, why would you want to bother about such trivial aspects as nano coloring? Don't waste time fine-tuning a car that's headed for the junkyard. I do appreciate your perspective... and in a sense you are right. The way I see it is... if I could get rid of these bright white characters over deep black background that bother my eyes so much whenever getting a nano screen to compose a message within mutt, thus making my experience with mutt so much more pleasant for the next few months (before switching to vim) - and it should take a couple of minutes to make such change when someone who has done it tells me how - then it's well worth doing. And secondly, just for the sake of being capable of doing so... Isn't this what being a linux user and a mutt user is all about? :)
Re: colors/mono: bold vs. bright
On Tue, Aug 14, 2001 at 01:46:00PM -0400, Ken Weingold ([EMAIL PROTECTED]) wrote: What is the difference between the colors' 'bright' attribute and mono's 'bold'? The Mutt manual says that 'bright' makes the color boldfaced, but it is definitely different than mono's bold, where bold makes the characters a but thicker, where 'bright' simply seems to make them brighter. It depends on your terminal. Some will show white as about a 50% gray and bright white as white, and similarly blue as almost navy and bright blue as royal blue. Others will show white as white, and bright white as bold white, and blue as royal blue and bright blue as bold royal blue. I go out of my way to use the latter, myself. :-) -Rich -- Rich Lafferty --+--- Montreal, Quebec, Canada | Save the Pacific Northwest Tree Octopus! http://www.lafferty.ca/|http://zapatopi.net/treeoctopus.html [EMAIL PROTECTED] ---+---
Re: colors/mono: bold vs. bright
On Tue, Aug 14, 2001 at 01:46:00PM -0400, Ken Weingold wrote: What is the difference between the colors' 'bright' attribute and mono's 'bold'? The Mutt manual says that 'bright' makes the color boldfaced, but it is definitely different than mono's bold, where bold makes the characters a but thicker, where 'bright' simply seems to make them brighter. 'bold' may be characters drawn with thicker lines and/or brighter lines (or neither). it depends on the terminal type and its configuration. mutt's only asking the terminal for 'bold' (there's no termcap/terminfo attribute for 'bright') -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: colors with wrapped quotes
Ken -- ...and then Ken Weingold said... % So sorry if this has been covered, but with mail coming from more % plebian :) mailers, I find that quoted text will wrap, so the end of *grin* At least they'll be threaded correctly, though, right? % a quoted line does not have the '' in the beginning. This of course % messes up the coloring, so the little pieces of the previous quoted % line is a different color. Anyone know a way of dealing with this? I suppose a procmail rule to delete any mail from those users is out of the question, right? :-) If I get annoyed I just 'e'dit the message, 'J'oin up the line(s) in vim, save it, and then read it again, but the same thing (probably dropping even more to the next line thanks to the additional indentation of two sets of quotes) will happen when the message turns around again. I could imagine a vim macro that would look for a line starting with a few (well, mebbe one is valid) indent_string chars, another line (maybe shorter than length X) without any, and another line with the same number of indent_string chars and would then go back to the upper line and join up the bare one... % % Thanks. HTH HAND % % % -Ken :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! PGP signature
Re: colors with wrapped quotes
On Wed, Aug 8, 2001, David T-G wrote: I suppose a procmail rule to delete any mail from those users is out of the question, right? :-) If I get annoyed I just 'e'dit the message, 'J'oin up the line(s) in vim, save it, and then read it again, but the same thing (probably dropping even more to the next line thanks to the additional indentation of two sets of quotes) will happen when the message turns around again. I could imagine a vim macro that would look for a line starting with a few (well, mebbe one is valid) indent_string chars, another line (maybe shorter than length X) without any, and another line with the same number of indent_string chars and would then go back to the upper line and join up the bare one... Thanks. For me it's not worth the effort this way, since I view a message and then usually delete it. -Ken
Re: colors with wrapped quotes
* David T-G ([EMAIL PROTECTED]) [010808 09:47]:
the question, right? :-) If I get annoyed I just 'e'dit the message,
'J'oin up the line(s) in vim, save it, and then read it again, but
the same thing (probably dropping even more to the next line thanks to
the additional indentation of two sets of quotes) will happen when the
message turns around again.
I could imagine a vim macro that would look for a line starting with
a few (well, mebbe one is valid) indent_string chars, another line
(maybe shorter than length X) without any, and another line with the
same number of indent_string chars and would then go back to the upper
line and join up the bare one...
What works really well in vim is to 'J'oin the lines, and then '{gq}'
them. Vim is smart about wrapping when all lines have the same
indent on them, so if you join them, set textwidth to an appropriate
value, and then re-wrap them, it will be well prepared for the next
iteration.
A macro might be able to just tell which lines need to be joined by
looking for lines without the and executing kJ, then once it was
done '1G','/^$','gqG' (to re-wrap just the body). An example this simple
would surely fail with multiple levels of indentation in a message,
though.
--
Vineet http://www.anti-dmca.org
Unauthorized use of this .sig may constitute violation of US law.
Qba'g gernq ba zr!|tr 'a-zA-Z' 'n-za-mN-ZA-M'
PGP signature
Re: Colors missing in a couple places
Hey Michael. Thanks for the tip, but that doesn't seem to affect anything. I'm afraid I haven't really spent much time learning the vim configuration syntax and commands, mostly I have just been using it to get stuff done. As a result, I don't really understand the vimrc files I use :| Anyway, thanks again. I will keep looking, and if you have any other suggestions, I'd appreciate them. Lou On 06/07/01 12:06 PM, Michael Baro sat at the puter and typed:' Hi! On Thu, Jun 07, 2001 at 12:27:36AM -0400, Louis LeBlanc wrote: I am getting my mutt configs nicely whipped into shape, but I am missing one thing: colors when reading or writing mail. I am using mutt 1.3.18i with the vvv patches, and I have the following lines in my .muttrc (I thought these were supposed to handle the task): set editor=vim -c '/^$/+1' -u '~/.mutt/mutt.vimrc' Try this in your .vimrc: hi mailSignature ctermfg=darkred hi mailQuoted1ctermfg=darkcyan hi mailQuoted2ctermfg=darkgreen hi mailQuoted3ctermfg=darkred hi mailQuoted4ctermfg=darkmagenta hi mailQuoted5ctermfg=darkblue hi mailQuoted6ctermfg=darkcyan hi mailQuoted7ctermfg=darkgreen hi mailQuoted8ctermfg=darkred hi mailquoted9ctermfg=darkmagenta Maybe this is what you've been looking for. Mick -- [Michael Baro] [[EMAIL PROTECTED]] [05323/922061] [ URL: http://www.heim2.TU-Clausthal.de/~snyder ] [ICQ: 67659177] [ PGP: http://www.heim2.TU-Clausthal.de/~snyder/mick_pgp_key.gpg ] Linux 2.2.17 up: 63 days, 22:46 - Accept no limits. -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ
Re: Colors missing in a couple places
Louis LeBlanc ([EMAIL PROTECTED]) said something to this effect on 06/07/2001: Hey all. I am getting my mutt configs nicely whipped into shape, but I am missing one thing: colors when reading or writing mail. I am using mutt 1.3.18i with the vvv patches, and I have the following lines in my .muttrc (I thought these were supposed to handle the task): set editor=vim -c '/^$/+1' -u '~/.mutt/mutt.vimrc' Syntax highlighting in your editor is a function of the editor. In vim, do :h highlight. Try :syn on to see if your copy of vim has syntax highlighting enabled (some versions, for example, the default RedHat vim packages, don't). If you built it yourself, it most liely does. If that doesn't do anything, make sure your TERM variable is set to something that understands colors, like rxvt or xterm-color (or possibly xterm, depending on which ncurses you are using). (darren) -- Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec
Re: Colors missing in a couple places
Louis LeBlanc ([EMAIL PROTECTED]) said something to this effect on 06/07/2001: The :syn check shows a boatload of 'muttrc*' groups, but nothing else, which implies to me that the vimrc I am using is geared more toward editing the .muttrc file. Am I right there? That sounds right. What does set ft tell you? Right now I get filetype=mail, which means vim thinks it's editing a mail message (which it is). Are here any explicit set ft= or set filetype= lines in the vimrc you are referencing in your $editor line? If so, the problem is that I am just using the wrong vimrc. Any idea where I can get the right one to start with? Try loading vim without a vimrc (vim -u /dev/null) and run: syn on set ft=mail set fo=trcq And see how that works out for you. As for the color commands in the .muttrc, I take it the body configs are strictly for the mutt builtin viewer. Maybe I am mistaken, though. That is correct. (darren) -- All pleasures cost at least the time they take.
Re: Colors missing in a couple places
Louis LeBlanc ([EMAIL PROTECTED]) said something to this effect on 06/07/2001: Ok, small victory. I removed the '-u .mutt/mutt.vimrc' option from my 'editor' definition, and now I get color in my composition window. Some of them, anyway. Smileys, URLS and email addresses are still not colored. The email addresses in the headers are magenta, the header fields are green, as are the values, though I have hdrdefault set to red/white. You need to have the appropriate highlighting commands in your vim config, not your mutt config, for them to show up in your editor. The two are completely different processes; the MUA spawns $editor; when $editor exits, the MUA reads in the file that $editor was editing. There is no shared configuration between the two other than command line stuff that may be included in $editor. Defining ft=mail (see below) will use mutt's default mail hightlighting. :hi will show you what they are, as well as give you ideas what to start customizing. As an aside, I always begin my vimrc files with set nocompatible, so that there are no ugly vi-isms getting in the way of the cool things about vim, like syntax highlighting. Quoted text, is colored correctly, but Quoted1 shows as cyan, though I have it defined as magenta. The sig shows as magenta, though I have it defined as blue. You need to grep through the vim docs for syntax highlighting. :help syntax will bring up syntax.txt from the vim help docs. Be warned, though, it's a lot more complex that mutt syntax highlighting, since it is signed for highlighting programming languages. There are many more types of highlighting to be done than in mutt. As an experiment, try: :hi Normal ctermfg=3 (to restore it, try :hi Normal ctermfg=7) Also try the other numbers, 0 - 8 in place of the 3. This will give you a feel for what you can customize. The ones I customize are: hi Normal ctermfg=white hi Search cterm=bold ctermfg=7 ctermbg=4 hi StatusLine cterm=bold ctermfg=7 ctermbg=4 hi StatusLineNC cterm=bold ctermfg=7 ctermbg=1 hi Visual cterm=bold ctermfg=7 ctermbg=1 hi ModeMsg cterm=bold ctermfg=7 ctermbg=1 There are cterm, ctermfg, and ctermbg; cterm is for using bold or underline, for example, and cterm[fb]g are for the foreground and background colors respectively. some interesting mail related ones are mailQuotedX, where X is from 1 tp 6: hi mailQuoted1 ctermfg=1 hi mailQuoted2 ctermfg=2 hi mailQuoted3 ctermfg=3 hi mailQuoted4 ctermfg=4 hi mailQuoted5 ctermfg=5 hi mailQuoted6 ctermfg=6 Season to taste. Also, check URL:http://www.vim.org/html/syntax.html. I also tried setting the editor variable with -u NONE (as per the vim docs) then executed the following: syn on set ft=mail set fo=trcq The syn command had the effect of turning the colors back on, the other commands didn't seem to affect anything. Thanks, Darren. The other commands turn on things like line breaking and stuff relevant to composing mail. They just don't do things that are as obvious as the syntax highlighting. Mail reading was still black and white. I noticed I had my pager set to 'less', which is fine, but it doesn't do vim coloration. I set it to vim and colors are back, but still no colored links, smileys, etc. I also came up with the -c 'map q :q ' option to make it recognise a single 'q' keystroke as a quit command. set pager=builtin will use the defined highlighting. This situation is identical to the editor one I described above; the pager is an external program that receives the mail message on stdin, unless you defined pager=builtin (which is the default). I think the above was a little rambling; if so, I apologize. (darren) -- Do what thou wilt shall be the whole of the Law. Love is the law, love under will.
Re: Colors when replying to messages
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 muttrcColorFieldcontained attachment body bold error hdrdefault header
index
syn keyword muttrcColorFieldcontained indicator markers message normal quoted
search signature
syn keyword muttrcColorFieldcontained status tilde tree underline
syn match muttrcColorFieldcontained \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
Re: Colors when replying to messages
On Thu, Apr 26, 2001 at 10:32:48AM +0200, Marco Fioretti wrote: 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. Hi, Assuming that mutt is calling vim as it's editor, then the file that you are looking for is: /usr/share/vim/vim56/syntax/mail.vim The file you found (/usr/share/vim/vim56/syntax/muttrc.vim) controls syntax highlighting for muttrc files. regards, Biju - Biju Chacko| [EMAIL PROTECTED] (work) Exocore Consulting | [EMAIL PROTECTED] (play) Bangalore, India | http://www.exocore.com -
Re: Colors when replying to messages
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
Re: colors
What does mutt -v return? On Mon, Apr 16, 2001 at 11:49:17PM +0200, Robert T.G. Tan muttered: | I added some colors to my .muttrc, but it doesn't have | the expected effect. So what's up with that? | | I am using a color terminal, Eterm, on a FreeBSD box.. | | Tnx, rotan. -- /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
Re: colors
I've already solved my problem, by setting TERM to the right value color-xterm but fyi mutt -v ~ 1.2.5i (2000-07-28) tnx, rotan. Jason Helfman([EMAIL PROTECTED])@2001.04.17 18:59:45 +: What does mutt -v return? On Mon, Apr 16, 2001 at 11:49:17PM +0200, Robert T.G. Tan muttered: | I added some colors to my .muttrc, but it doesn't have | the expected effect. So what's up with that? | | I am using a color terminal, Eterm, on a FreeBSD box.. | | Tnx, rotan. -- /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
Re: Colors aren't quite working
On Mon, Apr 09, 2001 at 10:30:53PM +0200 or thereabouts, Erika Pacholleck wrote: ( Apr-09-2001 ) Conor Daly --: This should work. color index red default "~l" color index brightred default "~N~l" color index brightyellow default "~N!~l" Try naming the color instead of default It *should* work but alas it doesn't. I'm using Mutt 1.2.5i (2000-07-28) System: Linux 2.2.16-22 [using slang 10401] Compile options: snipped them I am using the same mutt version, compile options identical BUT: linked against ncuses-5.2 the same .muttrc worked beautifully on an RH 6.2 box. Any thoughts? Just an idea what you might check, RH 6.2 slang or ncurses? Don't know about slang but I read somewhere that some variables have to be set (.profile or so) - as said, all just ideas. -- Erika AAARRR! from my .muttrc lists [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] lists issues techtalk grrltalk lists mutt-users mailman-users List mails don't get coloured. I added subscribe [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] subscribe issues techtalk grrltalk subscribe mutt-users mailman-users and it all worked! Interesting how the "Reply to list" works for "lists" but colours work only for "subscribe"d lists. All fixed, Thanks for suggestions. Conor -- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 7:33pm up 2 days, 4:44, 9 users, load average: 0.11, 0.04, 0.01
Re: Colors aren't quite working
On Fri, Apr 06, 2001 at 09:58:18PM +0200 or thereabouts, Michael Tatge wrote: Conor Daly muttered: On Thu, Apr 05, 2001 at 03:40:03PM +0100 or thereabouts, Ailbhe Leamy wrote: I have a number of lists defined which are recognised, for instance, by "L" to "reply to list" but are not recognised for colours. my colour entries in .muttrc are color index brightyellow default "~N" color index red default "~l" # colour list messages red color index brightred default "~N~l" # colour new list messages bright red Note the "list" rules are the *last* "index" rules in .muttrc but this colouring just doesn't happen. This should work. color index red default "~l" color index brightred default "~N~l" color index brightyellow default "~N!~l" It *should* work but alas it doesn't. I'm using 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: Linux 2.2.16-22 [using slang 10401] 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="/etc" SYSCONFDIR="/etc" ISPELL="/usr/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. the same .muttrc worked beautifully on an RH 6.2 box. Any thoughts? I'll have to go look at the bug database. Conor. -- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 1:22pm up 5 days, 3:02, 4 users, load average: 0.06, 0.05, 0.01
Re: Colors aren't quite working
( Apr-09-2001 ) Conor Daly --: This should work. color index red default "~l" color index brightred default "~N~l" color index brightyellow default "~N!~l" Try naming the color instead of default It *should* work but alas it doesn't. I'm using Mutt 1.2.5i (2000-07-28) System: Linux 2.2.16-22 [using slang 10401] Compile options: snipped them I am using the same mutt version, compile options identical BUT: linked against ncuses-5.2 the same .muttrc worked beautifully on an RH 6.2 box. Any thoughts? Just an idea what you might check, RH 6.2 slang or ncurses? Don't know about slang but I read somewhere that some variables have to be set (.profile or so) - as said, all just ideas. -- Erika
Re: Colors aren't quite working
Conor Daly muttered: On Thu, Apr 05, 2001 at 03:40:03PM +0100 or thereabouts, Ailbhe Leamy wrote: I have a number of lists defined which are recognised, for instance, by "L" to "reply to list" but are not recognised for colours. my colour entries in .muttrc are color index brightyellow default "~N" color index red default "~l" # colour list messages red color index brightred default "~N~l" # colour new list messages bright red Note the "list" rules are the *last* "index" rules in .muttrc but this colouring just doesn't happen. This should work. color index red default "~l" color index brightred default "~N~l" color index brightyellow default "~N!~l" HTH, Michael -- We are Pentium of Borg. Division is futile. You will be approximated. (seen in someone's .signature) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Colors aren't quite working
On Thu, Apr 05, 2001 at 03:40:03PM +0100 or thereabouts, Ailbhe Leamy wrote: OK, I have gone a little mad with colours, but I'm too lazy to actualyl read things, I prefer to have it land in my brain without my intervention. I'm getting oddness also with 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: Linux 2.2.16-22 [using slang 10401] 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="/etc" SYSCONFDIR="/etc" ISPELL="/usr/bin/ispell" To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the muttbug utility. I have a number of lists defined which are recognised, for instance, by "L" to "reply to list" but are not recognised for colours. my colour entries in .muttrc are color hdrdefault blue default color quoted brightgreen default color signature cyan default color indicator blue red color index yellow default "" color index brightyellow default "~N" color index red default "~l" # colour list messages red color index brightred default "~N~l" # colour new list messages bright red color error brightred default color status black brightred color tree brightmagenta default# the thread tree in the index menu color tilde brightmagenta default color message brightcyan default color normal default default color attachment brightmagenta default color search default green# how to hilite search patterns in the pager color header cyan default "^(To|Date|From|Subject):" color body red default "(ftp|http)://[^ ]+"# point out URLs color body white default [-a-z_0-9.]+@[-a-z_0-9.]+# e-mail addresses color underline brightgreen default Note the "list" rules are the *last* "index" rules in .muttrc but this colouring just doesn't happen. IMAP rocks over my previous version on rh6.2 (mutt-1.0.1i) but the colours worked correctly there. -- Conor Daly Met Eireann, Glasnevin Hill, Dublin 9, Ireland Ph +353 1 8064217 Fax +353 1 8064275 9:19am up 1 day, 22:59, 6 users, load average: 0.13, 0.07, 0.02
Re: Colors aren't quite working
Ailbhe Leamy wrote: Nothing I've tried has allowed me to colour ^X-(anything except X-Mailer:) seperately from X-Mailer: XMailer: always gets trapped in the X- colouring. Try specifying the X- coloring before the X-Mailer coloring, e.g. color header green black ^X-.*: color header white black ^X-Mailer: Good luck. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Colors aren't quite working
On (05/04/01 15:26), Wade A. Mosely wrote: Ailbhe Leamy wrote: Nothing I've tried has allowed me to colour ^X-(anything except X-Mailer:) seperately from X-Mailer: XMailer: always gets trapped in the X- colouring. Try specifying the X- coloring before the X-Mailer coloring, e.g. color header green black ^X-.*: color header white black ^X-Mailer: Sadly, this doesn't work. Nor does reversing the order. Is there a way to construct a muttrc-friendly regexp to match "^X-(.*!'Mailer'):" or something? Ailbhe -- Homepage: http://ailbhe.ossifrage.net/
Re: Colors aren't quite working
At 21:06 +0100 05 Apr 2001, Ailbhe Leamy [EMAIL PROTECTED] wrote: On (05/04/01 15:26), Wade A. Mosely wrote: color header green black ^X-.*: color header white black ^X-Mailer: color header green black ^X- color header white black ^X-Mailer: Works for me. I'm using the development version, but that shouldn't matter. Sadly, this doesn't work. Nor does reversing the order. Is there a way to construct a muttrc-friendly regexp to match "^X-(.*!'Mailer'):" or something? If for some reason the above doesn't work for you you could use a regexp like: x-([^m]|m[^a]|ma[^i]|mai[^l]|mail[^e]|maile[^r]|mailer[^:]+): Ugly but it should work. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Do not simplify the design of a program if a way can be found to make it complex and wonderful.
Re: Colors aren't quite working
On (05/04/01 16:39), Aaron Schrab wrote: color header green black ^X- color header white black ^X-Mailer: Works for me. I'm using the development version, but that shouldn't matter. If for some reason the above doesn't work for you you could use a regexp like: x-([^m]|m[^a]|ma[^i]|mai[^l]|mail[^e]|maile[^r]|mailer[^:]+): OK, neither of these work. Am I overloading mutt's ability to parse colours? Is my version of mutt weaker than another, and if so, where can I get the .deb for the other? Or should I give up, and use header order to make the vgrep easier, rather than colours? Ailbhe -- Homepage: http://ailbhe.ossifrage.net/
Re: Colors aren't quite working
On (05/04/01 16:39), Aaron Schrab wrote: color header green black ^X- color header white black ^X-Mailer: OK, so I start mutt in a different xterm and suddenly it works. After I've emailed to say "It still won't play nice!" I have no idea why. Thanks to everyone who helped. If anyone can tell me why neither :source-ing the .muttrc nor feeding it the :color commands direct while it was running worked, I'd be most grateful. Ailbhe contrite -- Homepage: http://ailbhe.ossifrage.net/
Re: Colors aren't quite working
Ailbhe Leamy wrote: On (05/04/01 15:26), Wade A. Mosely wrote: Ailbhe Leamy wrote: Nothing I've tried has allowed me to colour ^X-(anything except X-Mailer:) seperately from X-Mailer: XMailer: always gets trapped in the X- colouring. Try specifying the X- coloring before the X-Mailer coloring, e.g. color header green black ^X-.*: color header white black ^X-Mailer: Sadly, this doesn't work. Nor does reversing the order. Is there a way to construct a muttrc-friendly regexp to match "^X-(.*!'Mailer'):" or something? Hmm... what I posted works for me without problems. I'm using Mutt/1.2.5i. -- Linux: The Choice of the GNU Generation
Re: Colors in Mutt
On Mon, Mar 12, 2001 at 04:01:45PM +0100, Olivier Billet wrote: Hi everyone, I have the following issue using mutt: it don't display the colors even though + I run it on a xterm_color (I can see colored prompt) + I have colors settings in my .muttrc What do I have to do ? Was there any option to include during the compiling phase? What does your .muttrc look like? -- David Rock [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- version 3.12 GIT$CS$ 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- PGP signature
Re: Colors when editing message
- Erika: It worked. And I promise to RTFM next time :) - all: Thanks a lot for all help. Ciao, Andreas -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99
Re: Colors when editing message
I am sorry for being so unprecise. I don't have a problem with the color of the background. I wanted the font of the qutoed text to be more bright. The second level quoted text is cyan, which is fine. Now I wanted the first level quoted text to be brightblue instead of blue. Thanks a lot up to here, Andreas On Mon, Mar 05, 2001 at 10:11:47AM +0100, Roel Vanhout wrote: Hi, Put this in your .vimrc: set background=dark cheers, roel On Mon, Mar 05, 2001 at 09:22:58AM +0100, Andreas Grytz wrote: Hello, I have a small problem with quoted text when I edit a messages (with vim). It's displayed blue on on black. I wanted to have the black background, but display the text brightblue. I don't know which/where I do have to set this color. Any hints? Ciao, Andreas -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99 -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99
Re: Colors when editing message
Hi, Put this in your .vimrc: set background=dark cheers, roel On Mon, Mar 05, 2001 at 09:22:58AM +0100, Andreas Grytz wrote: Hello, I have a small problem with quoted text when I edit a messages (with vim). It's displayed blue on on black. I wanted to have the black background, but display the text brightblue. I don't know which/where I do have to set this color. Any hints? Ciao, Andreas -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99
Re: Colors when editing message
Hi, set background=dark doesn't actually set your background to dark, it just tells vim that you use a dark background, and this way vim knows that it has to use light colors in the syntax highlighting. Anyway, in case you already knew this ;-), i would suggest downloading the vim reference guide from vim.org and start reading at p35, all the highlighting is described there, including how to change colors. But I must say that I have no problems with the default mail highlighting colors (on a dark background). cheers, roel On Mon, Mar 05, 2001 at 12:08:58PM +0100, Andreas Grytz wrote: I am sorry for being so unprecise. I don't have a problem with the color of the background. I wanted the font of the qutoed text to be more bright. The second level quoted text is cyan, which is fine. Now I wanted the first level quoted text to be brightblue instead of blue. Thanks a lot up to here, Andreas On Mon, Mar 05, 2001 at 10:11:47AM +0100, Roel Vanhout wrote: Hi, Put this in your .vimrc: set background=dark cheers, roel On Mon, Mar 05, 2001 at 09:22:58AM +0100, Andreas Grytz wrote: Hello, I have a small problem with quoted text when I edit a messages (with vim). It's displayed blue on on black. I wanted to have the black background, but display the text brightblue. I don't know which/where I do have to set this color. Any hints? Ciao, Andreas -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99 -- Andreas Grytz | http://www.linux-user.de Stefan-George-Ring 24 | Tel: +49 (0) 89 993411-0 D-81929 Mnchen | Fax: +49 (0) 89 993411-99
Re: Colors when editing message
( Mon, 05 Mär 2001 ) Andreas Grytz -- : I am sorry for being so unprecise. I don't have a problem with the color of the background. I wanted the font of the qutoed text to be more bright. The second level quoted text is cyan, which is fine. Now I wanted the first level quoted text to be brightblue instead of blue. Depends on how all you files look like, for example do you use all defaults, do you have your own defined syntax file, what is your ~/.vimrc already doing or do you use the systemwide rc file ?? Ok, I just assume you have a ~/.vimrc and all it does is something like syntax on or similar to get you some colors. For an already loaded file try this command in execution mode :so $VIMRUNTIME/syntax/mail.vim (Doppelpunkt so ...) If the result is different from your actual, put in your ~/.vimrc: source $VIMRUNTIME/syntax/mail.vim Restart vim and check whether you get the same as seen before. If not, you might change the line where you put it. The default definitions for colours are in those 2 files /usr/share/vim or similar, subdir /syntax/ and then 1. synload.vim 2. mail.vim As far as I can see from my mail.vim all quoting levels are colored as Comment and as Identifier which is in synload.vim defined cyan with additions which my console interpretes equally as BrightCyan. So then all your quote levels should ideally be brightcyan then. 3. hint: for colors there is also a colortest.vim If that worked copy that $VIMRUNTIME/syntax/mail.vim somewhere to your home and adjust the mailQuotedx lines according to the color each quote level should have. In case you have defined other colors somewhere, you should know which file to take for reference. Load your mail again, this time do a ":so /path/to/mymail.vim" and check whether it works (should be fine now) and then replace the sourcing path in your .vimrc by this one. For detailed information see a subdir called doc/ for a file called syntax.txt. ;-) Erika
Re: Colors not working?
On Thu, Nov 02, 2000 at 03:13:56PM -0500, Charles Krug wrote: List: My colors aren't working. My choices seem to be grey on black or black on black. I thought perhaps there was a problem with how I'd installed slang, but slrn seems to work perfectly well with colors and things. Good news! I found something dreadfully obvious I was missing. slang requires that the COLORFGBG variable be set. Setting it fixed my colors. Thanks to anyone who already sent an answer. Charles -- Charles Krug, Jr. Applications Engineer Pentek Corp 1 Park Way Upper Saddle River, NJ 07458
Re: colors for the indicator (more)
On Wed, Jul 26, 2000 at 12:02:58AM +0300, Mikko Hänninen wrote: No, you can't use that. The subscribe command takes a substring (well, regular expression) to match for in recipient addresses. It won't pay any attention to whatever aliases you have defined. Is it really a regexp? I'm also not sure about the substring. My muttrc contains `subscribe @bugs.guug.de', but mails sent to [EMAIL PROTECTED] (where 42 is any string) are not matched by ~l. Marius Gedminas -- Power corrupts, but we need electricity.
Re: colors for the indicator (more)
On 2000-07-26 10:04:28 +0200, Marius Gedminas wrote: Is it really a regexp? I'm also not sure about the substring. My muttrc contains `subscribe @bugs.guug.de', but mails sent to [EMAIL PROTECTED] (where 42 is any string) are not matched by ~l. It's a substring which is matched against the beginning of a mail address. That is, you can easily use things like these: subscribe mutt-users subscribe [EMAIL PROTECTED] etc., and they will work as intended. However, you can't do things like this: subscribe @securityfocus.com -- Thomas Roessler [EMAIL PROTECTED]
Re: colors for the indicator (more)
TLR, et al --
...and then Thomas Roessler said...
% On 2000-07-26 10:04:28 +0200, Marius Gedminas wrote:
%
% Is it really a regexp?
...
% `subscribe @bugs.guug.de', but mails sent to [EMAIL PROTECTED]
%
% It's a substring which is matched against the beginning of a mail
...
%
% etc., and they will work as intended. However, you can't do things
% like this:
%
% subscribe @securityfocus.com
One could probably do
subscribe .*@securityfocus.com
or perhaps ("the beginning of a mail address"?) even
subscribe [EMAIL PROTECTED]
right?
%
% --
% Thomas Roessler [EMAIL PROTECTED]
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
Re: colors for the indicator (more)
On 2000-07-26 09:42:06 -0400, David T-G wrote:
One could probably do
subscribe .*@securityfocus.com
or perhaps ("the beginning of a mail address"?) even
subscribe [EMAIL PROTECTED]
No. The matching is done with strncmp.
--
Thomas Roessler [EMAIL PROTECTED]
Re: colors for the indicator (more)
Johannes Zellner [EMAIL PROTECTED] wrote on Tue, 25 Jul 2000: 2) can the list names as supplied for `list' and `subscribe' be aliases? And if so: is the order there important ? -- e.g. can I use (in this order) subscribe mutt alias mutt mutt users [EMAIL PROTECTED] No, you can't use that. The subscribe command takes a substring (well, regular expression) to match for in recipient addresses. It won't pay any attention to whatever aliases you have defined. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / "OK, I'm weird, but I'm saving up to be eccentric."
Re: colors for the indicator (more)
Johannes Zellner muttered: 1) color indicator red yellow pattern ^ I guess you mean index here. The object indicator does not need any pattern. And mutt doen't accept one. does not seem to work as expected. If I use for example [0-9]+ as pattern, all lines which contain a digit somehwere are completely highlighted -- I'd expect only the digits to be highlighted as it is the case when specifying patterns for the body. Right, the index highlighting is 'line based'. That's the way I would expext it to work :) How would you color a pattern like ~D or ~z if it wasn't so? HTH, Michael -- Martin was probably ripping them off. That's some family, isn't it? Incest, prostitution, fanaticism, software. -- Charles Willeford, "Miami Blues" PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Colors, a wish ...
* Marius Gedminas [EMAIL PROTECTED] (Thu, Jun 08, 2000 at 10:55:04PM +0200) On Thu, Jun 08, 2000 at 10:01:42AM +0200, Gerhard den Hollander wrote: now what would be nce if I could do something like (pseudosyntax) color index from_the_boss yellow default color index priority=urgent bright default which means that normal messages are default message that are tagged urgent are set in the bright default color messages from the boss in yellow and urgnet messages fom the boss in bright yellow You can already do that: color index yellow default '~f [EMAIL PROTECTED]' color brightdefault default '~h "^x-priority: urgent"'# or whatever color brightyellow default '~f boss ~h "^x-priority: urgent"' # both Cool ! Thanks Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Sex is more fun than logic =`\, One cannot prove this, but it IS (=)/(=) In the same sense that Mt Everest IS or that Alma Cogan ISN'T
Re: Colors, a wish ...
On Thu, Jun 08, 2000 at 10:01:42AM +0200, Gerhard den Hollander wrote: now what would be nce if I could do something like (pseudosyntax) color index from_the_boss yellow default color index priority=urgent bright default which means that normal messages are default message that are tagged urgent are set in the bright default color messages from the boss in yellow and urgnet messages fom the boss in bright yellow You can already do that: color index yellow default '~f [EMAIL PROTECTED]' color brightdefault default '~h "^x-priority: urgent"'# or whatever color brightyellow default '~f boss ~h "^x-priority: urgent"' # both Check sections 3.7 and 4.2 for complete documentation. IIRC if multiple patterns match the last one is used. Unfortunately the manual is silent about this. Marius Gedminas -- "Cogito ergo I'm right and you're wrong." -- Blair Houghton
Re: Colors
At 05:53 AM 1999/11/15 +0200, you wrote: Reed Lai [EMAIL PROTECTED] wrote on Sun, 14 Nov 1999: or update ncurses to 5.0, and make sure the old version of ncurses has been purged or warped to new version... but carefully, purge ncurses may cause some curses-programs (telnet, telnetd, man...) to stop work. telnet and telnetd use curses? I would think that's very strange. Especially telnetd which is a daemon... ...I don't know why, but after I deleted libncurses.so.3.4, I can not telnet in(request the service of telnetd) and telnet out from that host. If I do that, telnet will tell me that it can not load libncurses.so.3.4... and when I warped it to new version of ncurses, then it works. I think, telnet use function calls from ncurses... Brgds Reed
Re: Colors
++ 13/11/99 11:37 -0500 - Subba Rao: Each time I start mutt, I get the following errors. Error in /home/subb3/.muttrc, line 65: default: no such color Change default to black (or whatever your background is or should be) and i guess your problem is gone. -Rejo. -- = Rejo Zenger [Sister Ray Crisiscentrum] [EMAIL PROTECTED] = http://mediaport.org/~sister PGP: see headers
Re: Colors
At 09:07 PM 1999/11/13 +0100, you wrote: ++ 13/11/99 11:37 -0500 - Subba Rao: Each time I start mutt, I get the following errors. Error in /home/subb3/.muttrc, line 65: default: no such color Change default to black (or whatever your background is or should be) and i guess your problem is gone. or update ncurses to 5.0, and make sure the old version of ncurses has been purged or warped to new version... but carefully, purge ncurses may cause some curses-programs (telnet, telnetd, man...) to stop work. delete config.cache config.status config.log, then re-configure after configure, you can look into config.h, if there is statement "#define HAVE_USE_DEFAULT_COLORS 1", then your default color will be fine (after re-compile, re-install) hope help reed
Re: Colors
Subba Rao [[EMAIL PROTECTED]] wrote: How do I get colors to work in Xterm? The "showrgb" command lists the color that are available. I can create Xterm with various colors. The color setting in .muttrc, do not seem to be working. Make sure your $TERM is set to a term that's defined to have colors, such as xterm-color. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Re: Colors in index
On Fri, Aug 13, 1999 at 01:12:19PM +0300, Denis Chapligin wrote: Hi I wanna make next thing: depending on "To:" field paint items in index by different colors. I added to .muttrc next lines: set index_format" %t " color index read black "^chollya" Try this: color index red black "~t chollya" but only letters from me([EMAIL PROTECTED]) to [EMAIL PROTECTED] are colored, letters from other senders are not. Where is mistake? When you only use a regular expression as your pattern mutt matches it according to the variable simple_search, which by default is set to match by sender or subject. Jimmy - [EMAIL PROTECTED]
Re: colors mailcap in 0.95
Benjamin Carter [EMAIL PROTECTED] wrote: application/octet-stream; cat "%s"; copiousoutput text/*; cat "%s"; copiousoutput Should mutt be quoting the parameter it passes? Mutt does do that. Whether it "should" has been the subject of some debate. Mutt is trying to be secure, by doing the quoting for you, but since no other MIME-related program does that quoting, it causes problems when they share a common mailcap file. I (and others) have solved this by writing a separate mailcap especially for Mutt, and pointing Mutt to it using $mailcap_path. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: colors in mutt
On Fri, 19 Feb 1999, Michael Sanders wrote: Unlike my previous version of rxvt, which set TERM=xterm-color, this version, by default, has TERM=xterm. I now must invoke mutt with Exec rxvt -tn xterm-color -T Mutt -e mutt Thanks this helped me figure out the problem. When runing tcsh you shall not run "setenv TERM xterm-color" but "set term=xterm-color" dont know the difference, but now it works! Thanks. regards, Allan -- This message is transmitted on 100% recycled electrons.
