recompile for updated ncurses?
I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any reason to recompile mutt? Thanks. -Ken
Re: test command in mailcap not recognizing %s
On Fri, Jul 27, 2001 at 12:29:09AM -0400, Joel Hammer wrote: I don't know how to make mutt distinguish between pdf and word (doc) documents. They both show up as octet stream. So, I am trying to put a test command into my mailcap file to test which type of file is attached, doc or pdf. I am not having much luck, so I think I need some help. This is a common problem. One solution has been to write a script that is invoked to view any application/octet-stream attachment and let that script choose the appropriate viewer based on the file name extension of the attachment. For an example, see http://www.spocom.com/users/gjohnson/mutt/#octet Another solution has been to modify mutt itself to scan the mime.types file for the application type corresponding to the file name extension, then scan the mailcap file again to find the viewer for this application type. I don't have a reference handy for this patch, but it's been discussed in the mutt-dev list. Here is my mailcap line for pdf: application/octet-stream;/opt/Acrobat3/bin/acroread %s; test=/usr/local/bin/mutt-testpdf %s Here is my script to test for the pdf file: echo This is 0 $0 /home/jlh/junk echo This is 1 $1 /home/jlh/junk echo This is all $* /home/jlh/junk i=`echo $0 | sed -n /\.pdf$/p` [ -n $i ] echo 0 || echo 1 Now, I have found many difficulties. First, %s never gets carried over into my script, which I test by looking at that junk file. I've noticed that, too. I don't know why it seems to work every place except the test field. If I put a constant string in place of %s, then it shouws up as $1. $0 shows the name of the command. I thought that sh -c makes the first argument $0, not $1. Nope. $0 is always the name by which the command was invoked and $1 is always the first argument. Finally, if I make my test script just echo a 1, acroread is still invoked. 'echo 1' will put an ASCII 1 on your script's stdout. You want to set the return value of the script, which is done with the 'exit' command, e.g., 'exit 0' for success and 'exit 1' for failure. Since the exit status of a script is the exit status of the last command, you could simply end your script with test -n $i Of course, your script isn't going to work since you can't pass it the file name, but at least you've learned a little about shell scripts. So, I am really confused. Any insight appreciated. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: recompile for updated ncurses?
Ken Weingold mutt [18/08/01 03:06 -0400]: I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any reason to recompile mutt? Reason? See if something breaks - if so recompile (nothing should, ideally) -suresh
Re: Make it simple?
On Fri, Aug 17, 2001 at 05:17:40PM -0400, Adam Shostack wrote: Hi, I just upgraded to mutt 1.2.5, and its insisting on coloring everything. I managed to get close to what I want by commenting HAVE_COLOR out of config.h, but now I still get things like underlining quoted text, boldface in headers, etc. I want plain text. Suggestions for how to get there? Set all your colours to grey in the .muttrc file? Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 PGP signature
Re: mutt porting to Max OS-X ?
msg.pgp
Re: recompile for updated ncurses?
Ken Weingold writes: I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any reason to recompile mutt? I'm following the ncurses snapshots and don't usually recompile mutt, but in your case, I'd recommend it if you are using shared libs for ncurses. If you check out the top of the NEWS file in ncurses, you'll find that a tremendous amount of stuff has changed since 5.0. The ncurses update won't affect mutt if the libs are compiled in statically.
Indent_string..
When I answer a mail mutt always put as quote on the last mail according to the indent_string in my .muttrc. I want only when no other has replyed, but if there already is a then i want it to become just How do I fix this? /d -- Bob Barker: Which one of these lovely womanoids will take home atomic tiara?
Re: recompile for updated ncurses?
On Sat, 18 Aug 2001, Ken Weingold wrote: I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any reason to recompile mutt? perhaps (with 5.1/5.2, I added a function assume_default_colors(), which you may want to configure against if you weren't using the default colors support in mutt). -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
procmail
Hi, Does anybody use procmail for sorting incoming mail? proc won't sort messages (I've tired test explained on faq page). Or, maybe I shell use fetchmail for receiving messagess? Please help, I'm a complete beginer, not only in mutt but also in Linux (: [p.s. ang my english is terrible] -- poz. azz.
Re: procmail
Azzazel mutt [18/08/01 20:26 +0200]: Does anybody use procmail for sorting incoming mail? Several of us do. proc won't sort messages (I've tired test explained on faq page). Or, maybe I shell use fetchmail for receiving messagess? Please help, I'm a complete beginer, not only in mutt but also in Linux (: http://www.hserus.net/dlhowto.html - and the procmail FAQ at http://www.iki.fi/~era/procmail (or just man procmailex at the shell prompt) should help you. -suresh
Re: recompile for updated ncurses?
On Sat, Aug 18, 2001, Suresh Ramasubramanian wrote: Ken Weingold mutt [18/08/01 03:06 -0400]: I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any reason to recompile mutt? Reason? See if something breaks - if so recompile (nothing should, ideally) Because of http://www.gnu.org/software/ncurses/ncurses.html. NOTE: A few applications will have to be recompiled (about 1% of the programs in a typical Linux distribution, 10% of the programs that use ncurses). These are easy to identify with nm or strings. Not sure what to make of nm or strings though. Thanks. -Ken
Re: pgp
On Fri, Aug 17, 2001 at 07:04:31PM -0700, Will Yardley wrote: David Rock wrote: You should be able to remove his key from your keyring. I would think that would fix it. yes that's what i would think too. but it doesn't appear to be there as far as i can tell (again i'm not a huge pgp expert): this is how i would view my keyring, right? zugzug% pgp -kv Pretty Good Privacy(tm) 2.6.3a - Public-key encryption for the masses. (c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04 SNIP -- Sintax error in config file! (line 378) aborted! I don't have a lot of experience with pgp, I use gpg myself. The end of this looks like you have a config problem. Maybe it is having an adverse effect on something else. What is on line 378 in your config file? -- David Rock [EMAIL PROTECTED] PGP signature
Re: mailboxes and new mail notification
Hi Mark, On Sun, Aug 19, 2001 at 01:59:34AM +0100, Mark Hill wrote: Hello, I'm trying to get mutt to tell me if there is any new mail in an mbox folder. AFAIK, new messages come up when I go to change in to another dir, but instead mutt says 'mailboxes [0]' (or something like that.) I've added these mailboxes to ~/.muttrc like so: #mailboxes [...] mailboxes =sent-mail mailboxes /var/spool/mail/mark Personally I just do: mailboxes +mailbox1 +mailbox2 +mailbox3 And it works great, I press 'c' to change mailbox, and it will go to a mailbox which has new messages. - Morten. -- Morten Brix Pedersen [EMAIL PROTECTED] - http://www.wtf.dk/hp/ Copenhagen, Denmark. -- Programmer, Scout, Geek.
Re: procmail
proc won't sort messages (I've tired test explained on faq page). Or, maybe I shell use fetchmail for receiving messagess? Do you have a .forward file in your home directory? [jlh@cc846558-a jlh]$ cat .forward |exec /usr/bin/procmail Then, do you have mistakes in your .procmailrc file. Here is mine as an example of one that works: [jlh@cc846558-a jlh]$ cat .procmailrc # routes incoming mail to appropriate mailboxes PATH=/usr/bin:/usr/local/bin MAILDIR=/home/jlh/Mail LOGFILE=proclog SHELL=/bin/sh :0: * ^Reply-To.*[EMAIL PROTECTED] linux_users :0: * ^Reply-To.*netraverse.com Caldera :0: * ^Reply-To.*lists.caldera.com Caldera :0: * ^Reply-To.*ltsp.discuss Discuss :0: * ^From.* /var/spool/mail/jlh Now, I forget just how you make your mail agent honor the .forward file. That will be left as an excersize to the student. Let me know when you find out. Check your LOGFILE to look for errors, etc. (Just noticed my log file is empty. No idea why.) Don't forget those . in front of the file names. Joel
Re: mailboxes and new mail notification
Mark Hill mutt [19/08/01 01:59 +0100]: #mailboxes mailboxes ! mailboxes =blackbox Try mailboxes `echo $HOME/Mail/*` -suresh
Re: procmail
Joel Hammer mutt [18/08/01 21:50 -0400]: Now, I forget just how you make your mail agent honor the .forward file. That Your MTA you mean? See, if you run sendmail on linux, there's no need to have a .forward, as sendmail uses procmail as the LDA (local delivery agent). Then the usual reason why .forward is ignored is unsafe permissions on your homedir or your .forward / .procmailrc (should not be group-writeable). Check your mailserver logs. -suresh
Re: procmail
Then the usual reason why .forward is ignored is unsafe permissions on your homedir or your .forward / .procmailrc (should not be group-writeable). Unless you have one group per user, and procmail was configured accordingly. As appears to be the case with at least one major Linux distro. But why would anyone use Linux anyway ...
Re: mailboxes and new mail notification
On Sun, Aug 19, 2001, Mark Hill wrote: On Sun, Aug 19, 2001 at 07:26:11AM +0530, Suresh Ramasubramanian wrote: Mark Hill mutt [19/08/01 01:59 +0100]: #mailboxes mailboxes ! mailboxes =blackbox Try mailboxes `echo $HOME/Mail/*` -suresh Okay, I'm not too sure if this works as my ~/Mail/procmail.log was picked up as having new mail (I used it as mailbox previously.) I moved it somewhere else, expecting other folders to picked up, but they weren't. I'll wait for some 'real' new mail and see what happens. :) You can do it all on one line. And '!' means your spool folder. Try: mailboxes ! =blackbox HTH -Ken ps: please set some sort of line wrapping in your editor
