[1.2.5] resend-message
The resend-message function isn't documented in the manual. Moreover, it doesn't set the Bcc and Fcc fields (unlike the other send functions). -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ - 100% validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des Jeux Mathématiques et Logiques, TETRHEX, etc. Work: CR INRIA - computer arithmetic / PolKA research team at LORIA
Re: [1.2.5] resend-message
Vincent Lefevre writes: The resend-message function isn't documented in the manual. I submitted a patch for this back in August. It went straight into cvs (and 1.3.x). Moreover, it doesn't set the Bcc and Fcc fields (unlike the other send functions).
Error messages
When working on my .muttrc, it would be very nice if there were some way to see error messages generated by bugs in the .muttrc. Is there any such mechanism? -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley
compile mutt with pgp support
Hi guys! do you know how to tell "configure" command to append (activate) the PGP support into de Makefile. Thanks in advance. sorry this is urgent. _ Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
From: depending on To:
'lo I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. For example i want all my mail to be send with a "From: [EMAIL PROTECTED]", but when i send to "To: [EMAIL PROTECTED]" i want the "From: " to be "From: [EMAIL PROTECTED]". It wokrs fine untill i send the mail to [EMAIL PROTECTED] Then the "From: " is changed permanently to [EMAIL PROTECTED] How do i handle this to change "From: " back to [EMAIL PROTECTED] after sending the mail to [EMAIL PROTECTED]? -- k. PGP signature
Re: From: depending on To:
yeah, thats a common complaint around here with send-hook. not sure if its being worked on. ?? On Wed, Dec 13, 2000 at 06:47:43PM +0100, Jakub Klausa chortled: 'lo I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. For example i want all my mail to be send with a "From: [EMAIL PROTECTED]", but when i send to "To: [EMAIL PROTECTED]" i want the "From: " to be "From: [EMAIL PROTECTED]". It wokrs fine untill i send the mail to [EMAIL PROTECTED] Then the "From: " is changed permanently to [EMAIL PROTECTED] How do i handle this to change "From: " back to [EMAIL PROTECTED] after sending the mail to [EMAIL PROTECTED]? -- k. -- Prepare for the inevitable, and you will be struck by something worse. Before you speak, listen to my fist. Walk alone before you walk ahead.
Re: From: depending on To:
I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. Add another send-hook *before* the other one that resets this particual my_hdr: send-hook . 'unmy_hdr From:' send-hook '~t [EMAIL PROTECTED]' my_hdr From: ... I think I'll write up something for the manual ...
Re: From: depending on To:
On Wed, Dec 13, 2000 at 06:47:43PM +0100, Jakub Klausa wrote: I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. For example i want all my mail to be send with a "From: [EMAIL PROTECTED]", but when i send to "To: [EMAIL PROTECTED]" i want the "From: " to be "From: [EMAIL PROTECTED]". It wokrs fine untill i send the mail to [EMAIL PROTECTED] Then the "From: " is changed permanently to [EMAIL PROTECTED] How do i handle this to change "From: " back to [EMAIL PROTECTED] after sending the mail to [EMAIL PROTECTED]? Use a default sendhook. E.g.: sendhook . my_hdr "From: [EMAIL PROTECTED]"; I think it also needs to go before your other sendhooks that my_hdr From. And you might want to check the syntax in the manual. I'm running on _very_ little sleep. You also might consider setting from instead of using my_hdr. See the manual. -- Luke
Re: From: depending on To:
On Wed, Dec 13, 2000 at 09:57:49AM -0800, Mark Luntzel wrote: yeah, thats a common complaint around here with send-hook. not sure if its being worked on. huh? If you want a default value to be used with send-hook, just do something like: send-hook . my_hdr From: [EMAIL PROTECTED] send-hook some@address my_hdr From: [EMAIL PROTECTED] Each time you send an email, mutt will go through the list of hooks, and if one matches, it will execute it. '.' is used to specify the default. (it's a regex) This is clearly documented in the manual, isn't it? On Wed, Dec 13, 2000 at 06:47:43PM +0100, Jakub Klausa chortled: 'lo I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. For example i want all my mail to be send with a "From: [EMAIL PROTECTED]", but when i send to "To: [EMAIL PROTECTED]" i want the "From: " to be "From: [EMAIL PROTECTED]". It wokrs fine untill i send the mail to [EMAIL PROTECTED] Then the "From: " is changed permanently to [EMAIL PROTECTED] How do i handle this to change "From: " back to [EMAIL PROTECTED] after sending the mail to [EMAIL PROTECTED]? -- k. -- Prepare for the inevitable, and you will be struck by something worse. Before you speak, listen to my fist. Walk alone before you walk ahead. -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A PGP signature
Re: From: depending on To:
ok I am guilty of not digging deeply enough into the manual on this. thanks - On Wed, Dec 13, 2000 at 01:18:43PM -0500, Josh Huber chortled: On Wed, Dec 13, 2000 at 09:57:49AM -0800, Mark Luntzel wrote: yeah, thats a common complaint around here with send-hook. not sure if its being worked on. huh? If you want a default value to be used with send-hook, just do something like: send-hook . my_hdr From: [EMAIL PROTECTED] send-hook some@address my_hdr From: [EMAIL PROTECTED] Each time you send an email, mutt will go through the list of hooks, and if one matches, it will execute it. '.' is used to specify the default. (it's a regex) This is clearly documented in the manual, isn't it? On Wed, Dec 13, 2000 at 06:47:43PM +0100, Jakub Klausa chortled: 'lo I want my mutt to use different "From: " field values depending on the "To: " field. I managed to get it almost to work with the send-hook, but the problem is that the "From: " field changed with "my_hdr" directive doesn't get changed back to the default after sending the mail. For example i want all my mail to be send with a "From: [EMAIL PROTECTED]", but when i send to "To: [EMAIL PROTECTED]" i want the "From: " to be "From: [EMAIL PROTECTED]". It wokrs fine untill i send the mail to [EMAIL PROTECTED] Then the "From: " is changed permanently to [EMAIL PROTECTED] How do i handle this to change "From: " back to [EMAIL PROTECTED] after sending the mail to [EMAIL PROTECTED]? -- k. -- Prepare for the inevitable, and you will be struck by something worse. Before you speak, listen to my fist. Walk alone before you walk ahead. -- Josh Huber | [EMAIL PROTECTED] | 1024D/6B21489A 61F0 6138 BE7B FEBF A223 E9D1 BFE1 2065 6B21 489A -- Prepare for the inevitable, and you will be struck by something worse. Before you speak, listen to my fist. Walk alone before you walk ahead.
pic mailcap?
Hi all, Does anyone have a good mailcap addition for viewing gif or png pics? I would appreciate it. TIA.. -- Best regards, Gary Today's thought: Chaos, panic, pandemonium - my work here is done.
Re: pic mailcap?
Gary writes: Does anyone have a good mailcap addition for viewing gif or png pics? I would appreciate it. I use: image/gif; xv %s image/png; xv %s Unfortunately, this makes mutt wait for xv to exit, so I can't compare several images, or keep an image up while I read other mail. I've tried various combinations of adding to the string, but haven't found one that makes mutt keep the tmp file around long enough for xv to see it. (I thought "xv - -name image.png " would work, but it doesn't -- it apparently still depends on a temp file.) I've had the same "not waiting around long enough" problem with sending html messages to Netscape for viewing (as an alternate when they're too complicated to read with lynx). Has anyone found a trick to make mutt keep the tmp file around a little longer? It's not covered in the mailcap section of the mutt manual. ...Akkana
Re: pic mailcap?
On Wed, 13 Dec 2000, Akkana wrote: Gary writes: Does anyone have a good mailcap addition for viewing gif or png pics? I would appreciate it. I use: image/gif; xv %s image/png; xv %s Unfortunately, this makes mutt wait for xv to exit, so I can't compare several images, or keep an image up while I read other mail. I've tried various combinations of adding to the string, but haven't found one that makes mutt keep the tmp file around long enough for xv to see it. (I thought "xv - -name image.png " would work, but it doesn't -- it apparently still depends on a temp file.) I've had the same "not waiting around long enough" problem with sending html messages to Netscape for viewing (as an alternate when they're too complicated to read with lynx). Has anyone found a trick to make mutt keep the tmp file around a little longer? It's not covered in the mailcap section of the mutt manual. you can probably do what you want by making a simple shell script which copies the file given to a temporary file, runs xv and then removes it on exit: cp %1 $$ xv $$ rm -f $$ (basically - where you put the temp files, etc., is a matter for much discussion ;-) -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: pic mailcap?
On Wed, Dec 13, 2000 at 12:56:33PM -0800 or thereabouts, Akkana wrote: Does anyone have a good mailcap addition for viewing gif or png pics? I would appreciate it. I use: image/gif; xv %s image/png; xv %s Unfortunately, this makes mutt wait for xv to exit, so I can't compare several images, or keep an image up while I read other mail. I've tried various combinations of adding to the string, but haven't found one that makes mutt keep the tmp file around long enough for xv to see it. (I thought "xv - -name image.png " would work, but it doesn't -- it apparently still depends on a temp file.) Thanks for this.. I've had the same "not waiting around long enough" problem with sending html messages to Netscape for viewing (as an alternate when they're too complicated to read with lynx). Has anyone found a trick to make mutt keep the tmp file around a little longer? It's not covered in the mailcap section of the mutt manual. Just off the top of my head, maybe a wait command, or some such. I will play with it very late tonight when I get time. Thanks Akkana for your help. You know, as an afterthought, since starting Linux several months ago, I have tried ... maybe 20 different MUAs, and nothing compares to Mutt, nothing is faster, nothing allows me to go through 200 to 300 messages in about 15 - 20 mintues, and certainly nothing compares to the scoring or threading capabilities. .. I have always been a MUA-alohic, but I think I met my match. It does suck less g -- Best regards, Gary Today's thought: Chaos, panic, pandemonium - my work here is done.
Re: compile mutt with pgp support
Guido Sicoli muttered: do you know how to tell "configure" command to append (activate) the PGP support into de Makefile. It should be enabled by default, but you can explicitly enable it with configure --enable-pgp. see configure --help HTH, Michael -- Help! I'm trapped in a PDP 11/70! PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
gnupg vs pgp?
Just like the subject says. I see on the mutt homepage that gnupg is recommended over pgp. Are there reasons for this beyond the whole 'use gnu whenever possible because of their licensing'? Or are there real, functional reasons behind choosing gnupg over pgp? - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
Re: gnupg vs pgp?
Myrddin writes: Just like the subject says. I see on the mutt homepage that gnupg is recommended over pgp. Are there reasons for this beyond the whole 'use gnu whenever possible because of their licensing'? Or are there real, functional reasons behind choosing gnupg over pgp? Much better compliance with the OpenPGP (RFC2440) standard? Check out http://www.gnupg.org/.
Re: pic mailcap?
On Wed, Dec 13, 2000 at 12:56:33PM -0800, Akkana wrote:
Gary writes:
Does anyone have a good mailcap addition for viewing gif or png pics? I
would appreciate it.
I use:
image/gif; xv %s
image/png; xv %s
Unfortunately, this makes mutt wait for xv to exit, so I can't compare
several images, or keep an image up while I read other mail. I've tried
various combinations of adding to the string, but haven't found one
that makes mutt keep the tmp file around long enough for xv to see it.
(I thought "xv - -name image.png " would work, but it doesn't -- it
apparently still depends on a temp file.)
I put this in my mailcap:
image/*; mutt_bgrun xv %s; test=RunningX
The script mutt_bgrun takes care of creating a temporary file and
putting the viewer in the background:
tmpfile=/tmp/$LOGNAME$$${2##*/}
cp $2 $tmpfile
(
$1 $tmpfile
rm -f $tmpfile
)
I've had the same "not waiting around long enough" problem with sending
html messages to Netscape for viewing (as an alternate when they're too
complicated to read with lynx). Has anyone found a trick to make mutt
keep the tmp file around a little longer? It's not covered in the
mailcap section of the mutt manual.
I do something similar for Netscape, putting this in my mailcap:
text/html; mutt_netscape %s; test=RunningX
and using a script, mutt_netscape, containing basically the following:
tmpfile=/tmp/$LOGNAME$$${1##*/}
cp $1 $tmpfile
netscape -remote "openURL(file:$tmpfile, new-window)" 2 /dev/null ||
netscape $tmpfile
The netscape command returns immediately, so there's no way to know when
it's done with the file. I have a cron job that periodically cleans out
my old files from /tmp, so I haven't worried about it.
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | RF Communications Product Generation Unit
| Spokane, Washington, USA
Re: Error messages
On 2000.12.13, in [EMAIL PROTECTED], "Charles Curley" [EMAIL PROTECTED] wrote: When working on my .muttrc, it would be very nice if there were some way to see error messages generated by bugs in the .muttrc. Is there any such mechanism? You mean just to test the muttrc file and report parse errors? How about: mutt -F test.muttrc -f /dev/null -e "push x" /dev/null -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Error messages
Greetings!
At 2000/12/13/18:58 -0600 David Champion [EMAIL PROTECTED] wrote:
You mean just to test the muttrc file and report parse errors?
How about:
mutt -F test.muttrc -f /dev/null -e "push x" /dev/null
That's *way* cool!
Here's a script[1] which uses your idea to test $1 if it's defined and
$HOME/.muttrc if it isn't:
#!/bin/bash
pgm=`basename $0`
die () {
echo 12 "$pgm: $1"
exit 1
} # die
muttrc=$HOME/.muttrc.common
[[ -n $1 ]] muttrc="$1"
[[ ! -e $muttrc ]] die "$muttrc: no such file"
[[ ! -f $muttrc ]] die "$muttrc: not regular file"
[[ ! -r $muttrc ]] die "$muttrc: cannot open"
echo | mutt -F "$muttrc" -f /dev/null -e "push nnx" /dev/null
The "echo |" accounts for the situation where there are so many errors
that mutt prompts the user to hit the enter key:
source: reading aborted due too many errors in /etc/hosts
Press any key to continue...
The n's in front of the x in the push statement are to answer any
interactive mutt questions with "no" before exiting mutt. For
instance, because I don't use ~/Mail, mutt will ask me:
/usr/people/alban/Mail does not exist. Create it? ([y]/n):
and if I only pushed an "x" then then "x" would be used in an attempt to
answer the question. And "x" is not an acceptable answer to mutt. So
when a user ran the above script in this situation, the script would
appear to hang, because mutt was waiting for the answer to the question.
In addition, if the user knew enough to answer "n", the script would
*still* seem to hang. The reason is this. With "push x", the "x" would
have already been used in the first attempt to answer the question. And
because the "x" is no longer pending, it will not be used to exit, and
the mailbox is entered (even if it is /dev/null) and will sit there with
mutt awaiting the next command. Of course, the savvy user could enter
"nx" instead of just "n". The "echo" and the "push nnx" in the
script should make this unnecessary.
And if there are no interactive questions to be answered, then each
"n" causes mutt to harmlessly try to repeat a search that has never
been specified.
David
P.S. If you run this script and get:
[[: command not found
[[: command not found
[[: command not found
[[: command not found
you need to upgrade to bash 2.x.
[1] I call the script mutttest but undoubtedly there's a better name
than that for it.
--
Live in a world of your own, but always welcome visitors.
Re: special reply_regexp
On Wed, Dec 13, 2000 at 08:37:41AM +0100, Daniel Kollar wrote: Hi, in one of my folder containing msgs from a mailing list I would like to sort the msgs as threads. With the default reply_regexp this does not work, because the mailing list always puts a string "[ifc-ml:] " at the beginning of the subject line of each msg. is an increasing number and is always different. If mutt would check for the text after this string and possible Re:'s, then the threading display might work. Is this possible? If so, how should the reply_regexp look like? You can try "^(\[[][]*\][ \t]+)?(re([\[0-9\]+])*|aw):[ \t]*" \[[][]*\] should match: [ anything_except_brackets ] Or more specific: "^(\[[a-z0-9:-]*\][ \t]+)?(re ... " If you are sure that you can have only a-z0-9:- between the brackets. I've just tested that to tag messages and it worked. -- Laurent Pelecq [EMAIL PROTECTED]
