Re: spell checking
On Tue, Nov 07, 2000 at 02:36:55PM +0100, Frank Joerdens wrote: Is there a way to integrate some spell checking utility with mutt? I use vi as the editor . . . . If you're looking for spell checking while you're writing AND you're using vim, this highlights your spelling mistakes as you type: http://users.erols.com/astronaut/vim/index.html#Spelling Ben -- Benjamin KorvemakerFlying isn't dangerous. [EMAIL PROTECTED] Crashing is what's dangerous. PGP signature
Re: Searching in multiple mailboxes
On Mon, Oct 23, 2000 at 08:58:06PM +0200, Wouter Verheijen wrote: There is something that would be nice to have in Mutt: Searching in multiple (or all) mailboxes. Imagine this scenario: You are looking for a specified text in every message you have. It is only possible to search one mailbox, so this might be handy. See "grepm" and "grepmail" http://privat.schlund.de/b/barsnick/sw/grepm.html http://grepmail.sourceforge.net/ -- Benjamin KorvemakerDonkeys kill more people [EMAIL PROTECTED] annually than plane crashes. PGP signature
Re: Different signature/tag line each day/email.
On Wed, Oct 04, 2000 at 04:25:45PM -0600, Charles Curley wrote: On Wed, Oct 04, 2000 at 01:32:30PM -0700, Timothy Grant wrote: [snip] Problem is that I have two signatures, the formal one below, and an informal one. So I modified my script to take an argument depending on the sigfile I want to use. send-hook exceptionalminds.com set signature='(buildsig .siginformal)|' This doesn't work. and mutt spits up over it. How do I pass an argument to a script in my .muttrc? I don't think you do. [snip] What about: send-hook exceptionalminds.com 'set signature="(buildsig .siginformal)|"' (note the nesting of double quotes in single quotes) Ben -- Benjamin Korvemaker Windows is perfectly stable. [EMAIL PROTECTED] As long as you don't do anything unexpected. Like move the mouse. PGP signature
Re: Q: Why no replies to my post??
On Tue, Sep 26, 2000 at 09:38:49AM +0100, Dave Ewart wrote: [..] I'd appreciate any insights as to why my posting got no response! [..] I seem to recall I grumbled about a similar thing awhile back (also development series), and nothing anyone suggested worked for me. So I suffer through it when it happens. Or pipe it through "more" if I'm curious. My scenario being that sitting at a Linux box running X, xterms running sessions locally accented chars as "?", but xterms running sessions on a Solaris box display accented chars properly. Twiddling with locale settings or using --enable-locales-fix, neither seems to work. The *only* obvious thing I've found is differing versions of ncurses (4.2 on Linux, 5.0 on Solaris) and (a) I'm not root, so I can't upgrade the Linux one and (b) I ran into all sorts of grief (don't remember what it was, but I get the shakes thinking about it) trying to install my own copy. I'd love to hear some insights. Ben -- Benjamin KorvemakerA printer consists of three main [EMAIL PROTECTED] parts: the case, the jammed paper tray and the blinking red light. PGP signature
Re: Changing index display based on From:
On Fri, Jul 21, 2000 at 01:44:44AM +, George Klinich III wrote: Hi, Is there a way to change what is displayed in the index line for a message based on what is in the header? For example, if the From: matches a certain pattern, I'd like to see the the From field in the index line replaced by another header field. Thanks, George What about abusing the x-label: field with procmail and using %y in the index format? Ben -- Benjamin Korvemaker [EMAIL PROTECTED] If God had a beard, he'd be a UNIX programmer.
Re: Display of german 8 bit characters (Umlaute)
On Thu, Jul 13, 2000 at 11:23:29PM +0200, Michael Tatge wrote: Hi! Stephan Jaensch muttered: There's one issue tho that I am not able to resolve: The german hi-ascii characters (Umlaute, like äöü) are not displayed correctly in the pager, mutt places '?' there instead. Did you install charmaps-0.0.tar.gz? (see www.mutt.org) set charset="iso-8859-1" for the encoding. Mutt correctly displays Umlaute. Probably there's something wrong with the message. I saw for example this one in a german mail (aol mailer) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit VERY useful! Since mutt does what it's told - there are no öäü in us-ascii - it shows '?' instead. Maybe it's something similar? I've encountered a similar situation... I thought umlautes and stuff worked right earlier, but they don't now. Only on the linux machines, under X. Opening an xterm and rlogin'ing/ssh'ing in to solaris boxes to run mutt there works fine. Installing charmaps-0.0 didn't fix things. Nor setting LANG and LC_CTYPE. Running old versions doesn't seem to work, so it's possible something changed somewhere. The only significant difference I've found in configurations is that my Solaris version has +HAVE_LANGINFO_CODESET and the Linux version has -HAVE_LANGINFO_CODESET I notice vim and more don't have problems, so |more works ok for the rare occaisions it affects my life. Ben -- Benjamin Korvemaker Windows has detected that a gnat has farted [EMAIL PROTECTED] near your computer. Press any key to reboot.
Re: Seeking help
On Tue, Jun 13, 2000 at 10:38:32AM +0100, Lars Hecking wrote: keymap.c:69: `KEY_END' undeclared here (not in a function) This is what stopped the build - HP has a different flavor of cursess which should define this (curs_colr), but mutt's configure script doesn't recognize that (doesn't generate -I and -L options for the makefile to make it use the newer library). The only HP-UX 10.20 box I have access to has no man pages, and a compiler that truely sucks (no -g, no ansi). I cannot install anything on this machine. Which means that someone else will have to look into this ... My sympathy... Back when I last worked on an HP box, life was more dismal. (HP-UX v.OLD compiler didn't even want to compile g++) I heard rumors the compiler was intended for recompiling the kernel only. If you are allowed (this is important!) to install a version of gcc into your own space (and your space is big enough), then you can use gcc. simplified steps: 1. install gcc to $HOME/tmp/gcc 2. install mutt (with CC=$HOME/tmp/gcc) 3. delete $HOME/tmp/gcc [*] 4. use mutt [*] optionally, install gcc and keep it, and stay saner. That said, if you spend much time working on your HP-UX box, I suggest you ask the admins for a better compiler. Ben -- Benjamin Korvemaker [EMAIL PROTECTED]
Re: 'Abort unmodified message? ([y]/n):?
On Tue, May 09, 2000 at 06:22:06PM -0500, [EMAIL PROTECTED] wrote: Quoting Mikko Hänninen [EMAIL PROTECTED]: Kelly Scroggins [EMAIL PROTECTED] wrote on Tue, 09 May 2000: editor="vim -c "set tw=72" +1" set editor="vim -c 'set tw=72' +1" When I remove the double quoutes from the middle statement I get an error msg telling me there's an error on that line and it points to the 'tw'. So that didn't work. Don't remove them, change them to single quotes. Better yet, just for testing, try the simple: I didn't remove them. I replaced them. sorry, poor choice of words. Ok.. I've watched this thread FAR too long... (Although last time i de-lurked, I put my foot in my mouth, so take this with a grain of salt) what about putting something like this in your .vimrc: au BufEnter /tmp/mutt-*-*-* set tw=72 and keeping editor line nice and simple.. or am i missing something obvious? Ben -- Benjamin Korvemaker [EMAIL PROTECTED] I can't remember if I'm the good twin or the evil one.
Re: Forcing a rescan of folder
On Tue, May 02, 2000 at 12:36:46PM -0500, David DeSimone wrote: Mikko Hänninen [EMAIL PROTECTED] wrote: I use Maildir over NFS. I find myself frequently in a situation where I see in my incoming mail log that I've gotten mail in a particular folder while I'm reading it, but Mutt doesn't seem to notice it. It certainly takes much longer than the 5 seconds that the $mail_check value would indicate, assuming I understood its meaning correctly... I wonder if this could possibly be some sort of NFS caching issue or something? That would be quite unfortunate, as NFS is one of the main reasons to prefer maildir over other mailbox formats. Mutt does, though, appear to pay attention to the modified time on the directory, as an optimization for checking for new messages. So it looks like that could well be the issue. Try playing around with storing files in a directory from one NFS client, then examining the modified time of the directory from another client. Ugh. Hmm. it would seem NFS may be to blame. New mail was sent at 11:57, and presumably arrived within a few minutes. As can be seen, the "tmp" directory was modified at 11:58, but the "new" dir hasn't. Presumably, something might be wanted. (Using mutt-1.1.14) Fingers might be pointed at procmail (3.14), as I've checked (a) the machine I'm using, (b) the machine where the disk physically lives and (c) the machine doing the mail, and they all agree on the times coming out of stat. fort-kent[0-101]% stat * File: "cur" Size: 1536 Filetype: Directory Mode: (0755/drwxr-xr-x) Uid: ( 398/benjamin) Gid: ( 14/grad) Device: 0,13 Inode: 202758Links: 2 Access: Mon May 8 12:21:58 2000(0.00:07:06) Modify: Mon May 8 10:56:33 2000(0.01:32:31) Change: Mon May 8 10:56:33 2000(0.01:32:31) File: "new" Size: 512 Filetype: Directory Mode: (0755/drwxr-xr-x) Uid: ( 398/benjamin) Gid: ( 14/grad) Device: 0,13 Inode: 318215Links: 2 Access: Mon May 8 12:27:51 2000(0.00:01:13) Modify: Mon May 8 10:18:35 2000(0.02:10:29) Change: Mon May 8 12:29:02 2000(0.00:00:02) File: "tmp" Size: 512 Filetype: Directory Mode: (0755/drwxr-xr-x) Uid: ( 398/benjamin) Gid: ( 14/grad) Device: 0,13 Inode: 202782Links: 2 Access: Mon May 8 02:58:16 2000(0.09:30:48) Modify: Mon May 8 11:58:37 2000(0.00:30:27) Change: Mon May 8 11:58:37 2000(0.00:30:27) -- Benjamin Korvemaker [EMAIL PROTECTED] Capital punishment turns the state into a murderer. But imprisonment turns the state into a gay-dungeon master. - Emo Philips
Re: Forcing a rescan of folder
This might be on the way to tracking this down. New mail arrived while sending mail (between hitting "y" and regaining control of mutt). Mutt didn't catch new mail arriving, and couldn't be motivated to check the mailbox until more new mail arrived. Ben On Mon, May 01, 2000 at 05:55:57PM -0500, David DeSimone wrote: Benjamin Korvemaker [EMAIL PROTECTED] wrote: Can I force mutt to rescan the current folder (I'm using maildirs)? $ only commits the changes, but doesn't pick up the new mail in the box, yet gbuffy lets me know there's more mail. There isn't a function to cause a re-scan, because Mutt is simply supposed to do it without being told. There is a variable $timeout which tells Mutt how often to do it while waiting for commands, and there is another variable $mail_check which determines how often to do it when you are entering commands. They should have reasonable defaults, though. Anyway, Mutt is supposed to notice new mail without being told to look for it. -- 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 Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44 -- Benjamin Korvemaker [EMAIL PROTECTED] Hey! It compiles! Ship it!
Forcing a rescan of folder
I've probably just overlooked it, although I've looked a few times (when agravation exceeded laziness) and can't find it in the online help or user manual. Can I force mutt to rescan the current folder (I'm using maildirs)? $ only commits the changes, but doesn't pick up the new mail in the box, yet gbuffy lets me know there's more mail. Changing folders to the current folder works, but that commits/discards changes, and I don't necessarily want something that drastic. Thanks, Ben -- Benjamin Korvemaker [EMAIL PROTECTED]
listing number of messages in folder view
Is there a way to list the number of messages that are in a folder when listing the folders? (Checking the format strings in the manual doesn't seem to indicate so, but I may have overlooked the right place.) Even an indicator of which folders have old messages would be nice. I'm using mutt 1.0 (do I just need to upgrade to a development version?) and maildirs. Ben -- Benjamin Korvemaker [EMAIL PROTECTED] Two wrongs don't make a right, but three rights make a left.
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
Ok. Next time i'm just going to keep my mouth shut. At leat until
I've had a few cups of coffee.
On Thu, Mar 02, 2000 at 11:41:51PM -0600, Aaron Schrab wrote:
At 16:19 -0700 02 Mar 2000, Benjamin Korvemaker [EMAIL PROTECTED] wrote:
[delurk]
err. I just saw a complex answer that made my head spin. Mine's a bit
easier. I'm assuming you've got procmail already setup (or can figure
it out).
#
### Wherever you normal re-direct non-spool mail.
MAILDIR=Mail
XXX=`date +%s`.$$.`hostname`
You should be able to use $HOST instead of `hostname`.
# Set up a maildir for mutt
MUTT=IN.mutt/new/$XXX
:0:
Why are you having procmail use a lockfile? Not having to use lockfiles
is one of the major benefits to maildir. Besides, basically nothing
else will be using locking so it doesn't help.
[groan] good point. I just switched to maildirs and :0: is far too
habitual at this point. (/me goes and fixes magic scripts that
generate spam filters)
* ^TO_.*mutt
$MUTT
This will do the writing directly to the new subdirectory, which is bad.
In most cases there won't be a problem, but it could cause lost mail in
some situations. It's possible for procmail to be suspended between the
time it opens the file, and when it actually writes the message. If
some other program tries to read the message during this time it will
see an empty file (or possibly just part of the message). This is why
messages are supposed to be created in the tmp subdirectory, and moved
into new only after the whole message has been written.
[yuck] Blame it on my habit of skipping the first paragraph of
anything ('cause there's NEVER any important info in the into!).
Thanks for pointing out that my message should be purged from
everyone's memory and disk.
[going back into my hole. won't come out until I see my shadow.]
Ben
--
Benjamin Korvemaker
[EMAIL PROTECTED]
C makes it easy to shoot yourself in the foot. C++ makes
it harder, but when you do, it blows away your whole leg.
- Bjarne 'Stumpy' Stroustrup
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
[delurk] err. I just saw a complex answer that made my head spin. Mine's a bit easier. I'm assuming you've got procmail already setup (or can figure it out). # ### Wherever you normal re-direct non-spool mail. MAILDIR=Mail XXX=`date +%s`.$$.`hostname` # Set up a maildir for mutt MUTT=IN.mutt/new/$XXX :0: * ^TO_.*mutt $MUTT # Repeat ad-nauseum for things like spam. # Set up a maildir for your inbox INBOX=IN.inbox/new/$XXX :0: $INBOX # Leave DEFAULT alone so that if you reallly screw things up like I # did earlier today, procmail can still dump your mail into your # normal spool. (Or does it do that anyways?) # The only problem occurs when you're filing a message multiple times. Ben [lurk] On Thu, Mar 02, 2000 at 09:53:32AM -0800, Phil Staub wrote: On Wed, Mar 01, 2000 at 03:34:48PM -0500, Bennett Todd wrote: Here's a pretty safe maildir writer. Djb has some more rules for further paranoia; but the real world is not likely to bite you if you deliver messages like this. Written in Bourne Shell, but of course it codes into very lean, tight code in most any language. f=`date +%s`.$$.`hostname` cd $maildir cat tmp/$f mv tmp/$f new/ -Bennett Sorry for the bonehead question, but, assuming you were going to use this written as is (i.e., in Bourne shell) how would this be incorporated into a procmail recipe? Would you literally put this in the .procmailrc file, or write a shell script and invoke it from .procmailrc? Thanks, Phil -- Phil Staub Dragonfly Software Consulting Company. [EMAIL PROTECTED] 8196 SW Hall Blvd, Suite 104 503-641-3440 x33Beaverton, OR 97008 "Unix: because reboots are for hardware upgrades!" -- Benjamin Korvemaker [EMAIL PROTECTED] AI: Trying to get computers to behave like computers in the movies.
