Re: my_hdr and fcc-hook
Hi Cedric, * Cedric Duval [EMAIL PROTECTED] [010727 01:09]: * Thomas Huemmler [EMAIL PROTECTED] [07/27/01 00:23]: I´ve got a problem with my_hdr From: and fcc-hook. If my_hdr From: is set, Mutt doesn´t produce a Fcc-Line. Is this a bug? Looks like no fcc-hook is matching your mail. What are your fcc-hooks like? If they just use a simple regexp (i.e. without '~'), then they are evaluated according to the 'default-hook' variable. The default for default-hook is ~f %s !~P | (~P ~C %s) ^^^ As it uses ~P, perhaps you haven't correctly set your 'alternates' variable? I haven´t set 'alternates' at all. Now I have. Thanks a lot. :-) Thomas -- Thomas Hümmler * mailto:[EMAIL PROTECTED] * http://www.huemmler.de REDAKTIONSBÜRO T.O.M. * Gsprait 1 * D-85560 Ebersberg Phone: +49 (0 80 92) 8 38 33 Fax: +49 (0 80 92) 8 38 34 * am Kiosk: CHIP Linux-Spezial: KDE 2.1.1 für SuSE, Red HAT, Debian *
test command in mailcap not recognizing %s
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. 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. 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. Finally, if I make my test script just echo a 1, acroread is still invoked. So, I am really confused. Any insight appreciated. Joel
moving messages
How can I make a simple command for moving messages between folders? I don't see how it could be done with a macro that first copies and then deletes, since copy-message needs an argument from the user (the destination folder). -- Kalle Hasselström, [EMAIL PROTECTED] PGP signature
Re: moving messages
Am Fre, 27 Jul 2001, schrieb Kalle Hasselström: How can I make a simple command for moving messages between folders? I don't see how it could be done with a macro that first copies and then deletes, since copy-message needs an argument from the user (the destination folder). You can use the save-message command, it does exactly what you want. Gruß Christoph -- Christoph Maurer - Paul-Röntgen-Straße 7 - D - 52072 Aachen mailto:[EMAIL PROTECTED] - http://www.christophmaurer.de On my Homepage: SuSE 7.0 on an Acer Travelmate 508 T Notebook
Re: moving messages
On (27/07/01 07:51), Kalle Hasselström wrote: How can I make a simple command for moving messages between folders? I don't see how it could be done with a macro that first copies and then deletes, since copy-message needs an argument from the user (the destination folder). s saves messages to a different folder. T pattern - to tag all messages matching a pattern ;s new folder name - to move all tagged messages to a new folder Ailbhe -- Homepage: http://ailbhe.ossifrage.net/
(index/pager)_format size display
Is it possible to display the message size in a more human readable format than bytes? I'd like to see something like 20K or 3.3M if possible. Dan
Re: (index/pager)_format size display
Hi dan,
* dan radom [EMAIL PROTECTED] [010727 20:34]:
Is it possible to display the message size in a more human readable format than
bytes? I'd like to see something like 20K or 3.3M if possible.
your mail is more readable, if you limit the lines to 72 characters.
You´re looking for index_format? By default it has the value
%4C %Z %{%b %d} %-15.15L (%4l) %s
^^^
this one tells you the number of lines in the
message. Try the parameter c for Bytes.
HTH
Thomas
--
Thomas Hümmler * mailto:[EMAIL PROTECTED] * http://www.huemmler.de
REDAKTIONSBÜRO T.O.M. * Gsprait 1 * D-85560 Ebersberg
Phone: +49 (0 80 92) 8 38 33 Fax: +49 (0 80 92) 8 38 34
* am Kiosk: CHIP Linux-Spezial: KDE 2.1.1 für SuSE, Red HAT, Debian *
Re: (index/pager)_format size display
* dan radom [EMAIL PROTECTED] [07/27/01 12:15]: Is it possible to display the message size in a more human readable format than bytes? I'd like to see something like 20K or 3.3M if possible. I know that in the man page, for %c in index_format, it is said number of characters (bytes) in the message, but... have you tried it nevertheless? (or maybe %4c). It *normally* displays the number of bytes in a human readable format. -- Cedric
Is this a locking problem?
I've been running some of my old mailboxes through procmail/formail to resort a few things. I started getting some strange results and I noticed that several of my mailboxes have stuff like this: *It's important that you mFrom [EMAIL PROTECTED] Sun May 20 17:35:06 2001 Date: Sun, 20 May 2001 17:35:06 -0500 From: Chris Gentle [EMAIL PROTECTED] This should be the start of a new message in the mbox but as you can see the From line has been written into the middle of another message. This keeps mutt and formail from seeing the beginning of the new message and it's apparently just gobbled up by the first message. I'm going to have to try to straighten them out by hand with vim I suppose. I don't know how this could have happened but it seems to have the symptoms of a locking problem. Does mutt do any kind of locking on an mbox folder when you open it? I know there's some locking issues with NFS but these folders are on the local disk. Also, when mutt opens an mbox does it verify that the Content-Length: and Lines: headers are correct? Does it do anything about them if they are wrong? Are there any other utilities that might help straighten out this mess? -- Chris
Re: IMAP Check Interval?
On Friday, 27 July 2001 at 17:14, Mike A. Oligny wrote: Using 1.3.20i - is there any way to force mutt to check for new IMAP messages every [x] seconds? I think there used to be an option called imap_checkinterval or something... no more? With some other IMAP clients I have used, new mail shows up almost instantly... whether or not this is hard on the server, I want it! :) $timeout controls how often you poll the mailbox you're in. $mail_check controls how often you poll the mailboxes you've defined with the 'mailboxes' command. PGP signature
Two quick questions
Hi all! I've recently been hacking away at my .muttrc, and learning a whole lot in the process ;) There's two things though that I'd like to figure out (pointers to manpage entries welcome :). First, I'd like it if the builtin pager did NOT jump to the next message when I'm at the end and hit pagedown or down. I have the keys bound to next/prev line with arrows and next/prev page for page up/down. This is how I'd like to navigate, just not jumping to the next message automatically. I'd rather bind some keys like and to next/prev message. The next thing may be a vim thing or a mutt thing, I'm not too sure. When I reply or forward a message, it starts the cursor at the bottom of the message (under the quoted text), but above the sig. Any help on either of these would be greatly appreciated! Thanks! Kyle -- Kyle Knack Three o'clock in the afternoon is always just a little too late or a little too early for anything you want to do. -- Jean-Paul Sartre
Re: Two quick questions
On Fri, Jul 27, 2001 at 11:21:15PM -0400, Kyle Knack ([EMAIL PROTECTED]) wrote: First, I'd like it if the builtin pager did NOT jump to the next message when I'm at the end and hit pagedown or down. This is what I have in my .muttrc: # Do not move to next message when at the end # of a message and when invoking the next-page function. # Default behavior is so irritating set pager_stop The next thing may be a vim thing or a mutt thing, I'm not too sure. When I reply or forward a message, it starts the cursor at the bottom of the message (under the quoted text), but above the sig. Any help on either of these would be greatly appreciated! Thanks! If you want the cursor before your signature: set editor=vim +'/^-- /-1' -c 'set nohlsearch' That is one line before pattern /^-- / which is the standard way to start the signature. If you want the cursor before the reply but after the header: set editor=vim +'/^$/+1' -c 'set nohlsearch' That's one line after first empty line (end of header) -- Dominique
Re: Is this a locking problem?
It could be your procmail recipe which does not lock. Recipies that start with :0: use a lock, those which start with :0 do not use a lock. Example with lock: :0: * ^From foobar /.../foobar-maibox On Fri, Jul 27, 2001 at 05:36:36PM -0500, Chris Gentle ([EMAIL PROTECTED]) wrote: I've been running some of my old mailboxes through procmail/formail to resort a few things. I started getting some strange results and I noticed that several of my mailboxes have stuff like this: *It's important that you mFrom [EMAIL PROTECTED] Sun May 20 17:35:06 2001 Date: Sun, 20 May 2001 17:35:06 -0500 From: Chris Gentle [EMAIL PROTECTED] This should be the start of a new message in the mbox but as you can see the From line has been written into the middle of another message. This keeps mutt and formail from seeing the beginning of the new message and it's apparently just gobbled up by the first message. I'm going to have to try to straighten them out by hand with vim I suppose. I don't know how this could have happened but it seems to have the symptoms of a locking problem. Does mutt do any kind of locking on an mbox folder when you open it? I know there's some locking issues with NFS but these folders are on the local disk. Also, when mutt opens an mbox does it verify that the Content-Length: and Lines: headers are correct? Does it do anything about them if they are wrong? Are there any other utilities that might help straighten out this mess? -- Chris
