Re: Color Errors on Solaris
On Wed, May 23, 2001 at 05:11:39PM -0700, Igor Pruchanskiy wrote: mutt -v | grep System does it say [ncurses 4.2] or something like that ? if it does default should do, if you have no ncurses, i do not believe that it knows what default color is You can replace default with black or whatever you like, then it should not complain... again, i think he's getting the /usr/lib/libcurses.so in the mix (which i thought was svr4 curses) If you do not have ncurses i recommend that you go to www.sunfreeware.com and get yourself an ncurses package and then install it. after that recompile mutt and it should be able to find your ncurses and compile against it. after that you can set your TERMINFO env to point to /usr/local/share/terminfo since this is where ncurses will install all the terminfo entries and you can also set your TERM to color_xterm and then default will work just fine... I actually had to go through it this morning i wouldn't set the term to color_xterm, as thats not what dtterm is. if you want color_xterm, run a colr xterm igor On Wed 23 May 2001, Carl B . Constantine wrote: I've compiled Mutt 1.2.5 for Solaris 8 and do have some colors working in dtterm with a couple exceptions. First, anyone know how to get the standard dtterm to act more like the standard xterm with a black background? the inverse video in the options looks horrible with ANSI colors. Ok, now for my main problem. I'm getting the following errors when I start up mutt: (cconstan@viper): ~% src/mutt-1.2/mutt Error in /home/cconstan/.muttrc, line 283: default: no such color Error in /home/cconstan/.muttrc, line 284: default: no such color Error in /home/cconstan/.muttrc, line 285: default: no such color Error in /home/cconstan/.muttrc, line 286: default: no such color Error in /home/cconstan/.muttrc, line 287: default: no such color Error in /home/cconstan/.muttrc, line 289: default: no such color Error in /home/cconstan/.muttrc, line 290: default: no such color Error in /home/cconstan/.muttrc, line 291: default: no such color Error in /home/cconstan/.muttrc, line 292: default: no such color Error in /home/cconstan/.muttrc, line 293: default: no such color Error in /home/cconstan/.muttrc, line 294: default: no such color Error in /home/cconstan/.muttrc, line 295: default: no such color Error in /home/cconstan/.muttrc, line 296: default: no such color Error in /home/cconstan/.muttrc, line 297: default: no such color Error in /home/cconstan/.muttrc, line 298: default: no such color Error in /home/cconstan/.muttrc, line 299: default: no such color Error in /home/cconstan/.muttrc, line 300: default: no such color Error in /home/cconstan/.muttrc, line 301: default: no such color Error in /home/cconstan/.muttrc, line 302: default: no such color Error in /home/cconstan/.muttrc, line 305: default: no such color Error in /home/cconstan/.muttrc, line 312: default: no such color Error in /home/cconstan/.muttrc, line 315: default: no such color Error in /home/cconstan/.muttrc, line 316: default: no such color Error in /home/cconstan/.muttrc, line 317: default: no such color Error in /home/cconstan/.muttrc, line 318: default: no such color Error in /home/cconstan/.muttrc, line 319: default: no such color Error in /home/cconstan/.muttrc, line 320: default: no such color Error in /home/cconstan/.muttrc, line 321: default: no such color Error in /home/cconstan/.muttrc, line 322: default: no such color Error in /home/cconstan/.muttrc, line 324: default: no such color Error in /home/cconstan/.muttrc, line 326: default: no such color Error in /home/cconstan/.muttrc, line 327: default: no such color Error in /home/cconstan/.muttrc, line 328: default: no such color Error in /home/cconstan/.muttrc, line 329: default: no such color Error in /home/cconstan/.muttrc, line 330: default: no such color Error in /home/cconstan/.muttrc, line 331: default: no such color Error in /home/cconstan/.muttrc, line 333: default: no such color Error in /home/cconstan/.muttrc, line 334: default: no such color Error in /home/cconstan/.muttrc, line 335: default: no such color Error in /home/cconstan/.muttrc, line 337: default: no such color Error in /home/cconstan/.muttrc, line 338: default: no such color Error in /home/cconstan/.muttrc, line 339: default: no such color Error in /home/cconstan/.muttrc, line 340: default: no such color Error in /home/cconstan/.muttrc, line 341: default: no such color Press any key to continue... here is the relevant section(s) of my ~/.muttrc: ## = ## Color definitions ## = color attachment white magenta color body cyan default ftp://[^ ]* color body brightgreen default [[:alnum:]][-+.#_[:alnum:]]*@[-+.[:alnum:]]*[[:alnum:]] color body cyan default URL:[^ ]* color bold green default color
Re: Color Errors on Solaris
On Wed, May 23, 2001 at 05:42:43PM -0700, Carl Constantine wrote: On 5/23/01 17:11, Igor Pruchanskiy at [EMAIL PROTECTED] wrote: I'm on this list from home and work, so... ;-) after that you can set your TERMINFO env to point to /usr/local/share/terminfo since this is where ncurses will install all the terminfo entries and you can also set your TERM to color_xterm and then default will work just fine... I actually had to go through it this morning With this work with the standard CDE Console dtterm. It's basically brain dead otherwise. i haven't really had any problems with it, and i wouldn't call it braindead. not exactly full featured, but not brain dead. Quite frankly, I would like to run Gnome/Enlightenment instead of CDE and I will be looking into how to do just that very soon. i thought gnome was a sawfish thing now? dont really use it, i like motif. the newer releases of solaris 8 come with a freeware cd, that has kde, gnome, and loads of other open source packages compiled. even puts a gnome entry in the dtlogin menu. -- __ _ Carl B. Constantine / / (_)__ __ __[EMAIL PROTECTED] / /__/ / _ \/ // /\ \/ / (2.4.1)ICQ: 26351441 //_/_//_/\_ _/ /_/\_\ Stormix 2000 PGP key available on request Up the line - out the server- past the firewall - nothing but Net!! -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
mail mode for jed
In file sample.muttrc-tlr: set editor=/usr/local/jed/bin/jed %s -f 'mail_mode();' I was surprised to discover there is no any mail mode in the standard jed distribution. Is it available somewhere or just some minor private hack? -- choru::tek Life kills/
Re: color examples?
According to Damjan Lango on Tue, May 22, 2001 at 07:06:56PM +0200:
|
| Hi,
|
| Where can I find some nice examples for color configuration?
| It would be nice if mutt already included some examples...
| I do not have a good feeling what color configuration would be nice to use...
|
| ciao
| Damjan
Partly on loan from someone - this is what i use -
I change the status and other bars colors depending on what mailbox I
am viewing
Different senders have different colors (those that don't got to
/dev/null of course :) )
I have a reminder script, see the rules at the bottom for hour
warnings in different colors
I am too lazy to use perl or awk to line up the columns in this file.
But I guess in the time I erite these two sentences I could do it ...
ho hummm ...
# object foreground backg. RegExp
#
color body blue default
((ftp|http|https)://|(file|mailto|news):|www\\.)[-a-z0-9_.:]*[a-z0-9](/[^][{}
\t\n\r\()]*[^][{} \t\n\r\().,:!])?/?
color body blue default [-a-z_0-9.+]+@[-a-z_0-9.]+
color body reddefault (^| )\\*[-a-z0-9äöüß*]+\\*[,.?]?[ \n]
color body green default (^| )_[-a-z0-9äöüß_]+_[,.?]?[ \n]
color index blue default ~U # unread
color index red default ~F # Flagged
color index greendefault ~N # New
#color index yellow default ~Q ~D # Replied and deleted
color index magentadefault ~T # Tagged
color index yellow default ~Q # Replied
color index yellow default '~l'
color index brightyellow default '~N ~l'
color index cyan default ~h ^From:.*eric
color index cyan default ~h ^From:.*Fruitcom
color index blue default ~h ^From:.*clug
color index blue default ~h ^Subject:.*'has been active'
color index brightyellow default ~h ^Subject:.*'#'
color index brightyellow default ~h ^To:.*'reminder'
color index yellow default ~h ^From:.*dom
color index blue default ~h ^From:.*'root'
color index brightyellow default ~h ^From:.*rob
#color index yellowdefault ~R ^From:.*leon # Read from Leon
color index brightyellow default ~h ^From:.*leon
color index brightred default ~s ^todo
color index brightgreen default ~h ^From:[EMAIL PROTECTED]
color index brightblue default ~h ^From:.*Maersk
color index brightgreen default ~h ^From:.*houthoff
color index brightgreen default ~h ^From:.*kinman
#color index brightred default ~s urgent # Msg is urgent
#color index brightyellow default ~s \[rel\] # Msg is urgent
color index brightbluedefault ~s fruitcom
color index brightblue default ~D ~s fruitcom
color index yellow default ~s #
color index reddefault ~F
color index yellow default ~R # Read
color index blue default ~h ^Subject:.*'72 Hours'
color index yellow default ~h ^Subject:.*'48 Hours'
color index brightblue default ~h ^Subject:.*'24 Hour's
color index brightyellow default ~h ^Subject:.*'6 Hours'
color index reddefault ~D # Deleted
#color index brightred default ~a
#color normal whitedefault # normal text
#color indicator green red # actual message
color tree magenta default # thread arrows
color status brightcyan blue
color signature cyan default
color error yellow default # errors
color messageyellowdefault # info messages
#color signature reddefault # signature
color attachment yellow red # MIME attachments
color search yellow red # search matches
color tilde magenta default # ~ at bottom of msg
color markersreddefault # + at beginning of wrapped lines
#color hdrdefault green default # default header lines
color bold reddefault # hiliting bold patterns in body
color underline green default # hiliting underlined patterns in body
color quoted green default # quoted text
color quoted1magentadefault
color quoted2reddefault
color quoted3green default
color quoted4cyan default
color quoted5blue default
color quoted6magentadefault
color quoted7reddefault
color quoted8green default
color quoted9cyan default
--
Eric Smith
Re: mail mode for jed
Ups, this one was mis-addressed. - Forwarded message from Thomas Roessler [EMAIL PROTECTED] - From: Thomas Roessler [EMAIL PROTECTED] To: choru::tek [EMAIL PROTECTED] Date: Thu, 24 May 2001 12:20:48 +0200 Subject: Re: mail mode for jed User-Agent: Mutt/1.3.18i The latest version I'm using is here: http://www.does-not-exist.org/roessler/flower.sl http://www.does-not-exist.org/roessler/mail_mode.sl flower.sl is for text/plain; format=flowed; mail_mode.sl is the mail mode proper. flower extends and needs mail_mode. -- Thomas Roesslerhttp://log.does-not-exist.org/ - End forwarded message - -- Thomas Roesslerhttp://log.does-not-exist.org/
Verifying PGP/MIME messages
I'm trying to write a Perl script to verify PGP/MIME messages
generated by mutt. I can't even get gnupg to verify the messages
saved from mutt, though.
I save the message body and the signature as msg and msg.asc
repsectively, and run this command:
[squat ~] $ gpg --no-verbose --batch --output - --verify msg.asc msg
gpg: Signature made Thu May 24 02:44:15 2001 BST using DSA key ID 53F45D7D
gpg: BAD signature from Alisdair McDiarmid [EMAIL PROTECTED]
When mutt verifies it (according to my muttrc, using the same
command) it checks out as a good signature.
What is that I'm doing wrong here? How does mutt sign and verify
messages? Does anyone know of a seperate program that will verify
PGP/MIME signed messages?
Sorry if this is the wrong place to ask this, and thanks in advance.
--
#define p(s,f,a)if(strncmp((*v+strlen(*v)-3),s,3)==0)printf(f,a);else
main(unsigned n,char**v){char b[33];if(n!=2){printf(Usage: %s num\n
,*v);exit(1);}n=strtol(v[1],0,0);p(dec,%ld\n,n)p(hex,0x%X\n,n
){int i=32;b[i]=0;for(;i;){b[i-=1]=48+n%2;n/=2;}p(bin,%s\n,b);};}
Re: Color Errors on Solaris
On Thu, May 24, 2001 at 09:40:34AM +0100, Steve Kennedy wrote: On Wed, May 23, 2001 at 05:42:43PM -0700, Carl Constantine wrote: Quite frankly, I would like to run Gnome/Enlightenment instead of CDE and I will be looking into how to do just that very soon. If you look on Sun's site, there is a link to a company that is doing the porting work for GNOME to Solaris. Last time I looked they hadn't quite got 1.4 packaged, but it was expected real soon now. also, something i forgot to mention is that sun is ditching cde for gnome. and some funky webdesk stuff, but thats another story. im guessing at a release date of gnome 2.0/solaris 9 timeframe. heard their desktop group actually has ppl on the gnome team...also heard something about star office and open office getting together. Steve -- NetTek Ltd tel +44-(0)20 7483 1169 fax +44-(0)20 7483 2455 Flat 2,43 Howitt Road, Belsize Park,London NW3 4LU mobile 07775 755503 Epage [EMAIL PROTECTED] [body only] -- thanks adam any and all ideas herein are the sole property of the author, with no implied warranties or guarantees. unless its somebody else's already.
Weird -c 'vi tw=72' behavior
In my muttrc, I put the following to limit the number of characters per line to 72: set editor = vi -c 'set tw=72' When I compose a message in mutt, every time after I hit [enter] after typing in the subject, it spits out this: option, 1: set: no tw option: 'set all' gives all option values Press Enter to continue: Where am I going wrong? I ripped the tw=72 thing off someone else's muttrc that was on the net, but is it the wrong command to pass? Thanks for your help. - -Munish
Re: Weird -c 'vi tw=72' behavior
On Thu, May 24, 2001 at 11:14:37AM -0400, Louis LeBlanc wrote: On Thu, May 24, 2001 at 06:03:09PM +0200, Munish Chopra sat at the 'puter and typed: In my muttrc, I put the following to limit the number of characters per line to 72: set editor = vi -c 'set tw=72' When I compose a message in mutt, every time after I hit [enter] after typing in the subject, it spits out this: option, 1: set: no tw option: 'set all' gives all option values Press Enter to continue: Where am I going wrong? I ripped the tw=72 thing off someone else's muttrc that was on the net, but is it the wrong command to pass? You probably want this: set editor = vi -c 'set textwidth=72' That doesn't help (same thing). By the way, I'm running FreeBSD...without vim or fancy vi clones. Thanks for your help. Don't mention it. Lou -- Louis LeBlanc Fully Funded Hobbyist, KeySlapper Extrordinaire :) [EMAIL PROTECTED] http://acadia.ne.mediaone.netԿԬ -- -Munish
Re: Weird -c 'vi tw=72' behavior
darren chamberlain [mutt-users] Thu, May 24, 2001 at 12:18:37PM -0400: textwidth (and tw) are Vim things, not vi. On most Linux distributions, 'vi' is not real vi, but some vi clone (vim for RedHat, elvis for Slackware, nvi (I think) for Debian) renamed 'vi'. If you use vi, use the fmt command, or download par. -s -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Color Errors on Solaris
On Thu, May 24, 2001 at 02:33:48AM -0400, adam morley wrote: default is implemented for ncurses and slang, not for Solaris curses. solaris curses == svr4 curses, i think. /usr/lib/libcurses.a, etc. reason normal curses popped up is there are licensing issues with svr4 stuff. heck, download the source for solaris (sun's website) recompile libcurses with default for that matter. If you have Solaris 8 with the Software Companion installed, you have ncurses sitting in /opt/sfw/lib. Works great with Mutt. -Jeremy
Re: Color Errors on Solaris
On 2001.05.24, in [EMAIL PROTECTED], adam morley [EMAIL PROTECTED] wrote: If you look on Sun's site, there is a link to a company that is doing the porting work for GNOME to Solaris. Last time I looked they hadn't quite got 1.4 packaged, but it was expected real soon now. also, something i forgot to mention is that sun is ditching cde for gnome. and some funky webdesk stuff, but thats another story. im guessing at a release date of gnome 2.0/solaris 9 timeframe. heard their desktop group actually has ppl on the gnome team...also heard something about star office and open office getting together. This porting work is actually just for the fully-integrated version Sun wants to ship in the future. It's fully possible to compile and run it yourself, if you don't particularly want your windowing environment to support all the little things your OS does uniquely. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
check_new and mail_check
It seems I messed up my reply the first time, but what I wanted to ask was: I was wondering how often mutt checks for mail when check_new=yes is set? And is this affected by mail_check=5? Right now I have both of the above set, but whether both are set or only check_new, it doesn't seem to be doing much (I have fetchmail running every now and then, but I actually have to hit 'g' to check for new mail). -- -Munish
Re: Weird -c 'vi tw=72' behavior
On Thu, May 24, 2001 at 06:43:39PM +0200, Munish Chopra wrote: On Thu, May 24, 2001 at 11:14:37AM -0400, Louis LeBlanc wrote: On Thu, May 24, 2001 at 06:03:09PM +0200, Munish Chopra sat at the 'puter and typed: In my muttrc, I put the following to limit the number of characters per line to 72: set editor = vi -c 'set tw=72' When I compose a message in mutt, every time after I hit [enter] after typing in the subject, it spits out this: option, 1: set: no tw option: 'set all' gives all option values Press Enter to continue: Where am I going wrong? I ripped the tw=72 thing off someone else's muttrc that was on the net, but is it the wrong command to pass? You probably want this: set editor = vi -c 'set textwidth=72' That doesn't help (same thing). By the way, I'm running FreeBSD...without vim or fancy vi clones. In that case, use 'wm' (wrapmargin) instead of 'tw'. Wrapmargin does pretty much the same thing as textwidth, but the value is the size of the right margin. So, if you always edit in an 80-character-wide terminal, wm=8 is the same as tw=72. Try either of these: set editor = vi -c 'set wm=8' set editor = vi '+set wm=8' Use the second form if your vi is really old. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
Re: Color Errors on Solaris
On Thu, May 24, 2001 at 01:00:03PM -0500, David Champion wrote: On 2001.05.24, in [EMAIL PROTECTED], adam morley [EMAIL PROTECTED] wrote: If you look on Sun's site, there is a link to a company that is doing the porting work for GNOME to Solaris. Last time I looked they hadn't quite got 1.4 packaged, but it was expected real soon now. also, something i forgot to mention is that sun is ditching cde for gnome. and some funky webdesk stuff, but thats another story. im guessing at a release date of gnome 2.0/solaris 9 timeframe. heard their desktop group actually has ppl on the gnome team...also heard something about star office and open office getting together. Beta packages are being distributed by Ximian already (this is GNOME 1.4 / Solaris 8). For the last while, it's seemed that they will ship a heavily modified 1.4 with Solaris 9 sometime in October. And yes, they do have people on the gnome team, and Star Office and Open Office are even going as far as being 'merged' (heavily borrowing from each other). This porting work is actually just for the fully-integrated version Sun wants to ship in the future. It's fully possible to compile and run it yourself, if you don't particularly want your windowing environment to support all the little things your OS does uniquely. -- -D. [EMAIL PROTECTED]NSITUniversity of Chicago -- -Munish
Re: check_new and mail_check
On Thu, May 24, 2001 at 08:07:52PM +0200, Munish Chopra wrote: It seems I messed up my reply the first time, but what I wanted to ask was: I was wondering how often mutt checks for mail when check_new=yes is set? And is this affected by mail_check=5? Right now I have both of the above set, but whether both are set or only check_new, it doesn't seem to be doing much (I have fetchmail running every now and then, but I actually have to hit 'g' to check for new mail). This behavior is also affected by the 'timeout' variable. From the manual: This variable controls the number of seconds Mutt will wait for a key to be pressed in the main menu before timing out and checking for new mail. A value of zero or less will cause Mutt not to ever time out. The default value is 600, or 10 minutes. I put set timeout=10 in my muttrc and mutt now informs me of new mail at a much more reasonable interval. Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | RF Communications PGU http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
