Re: Changing attachment mime type
On 2002-09-10 10:40:46 -0300, Bruno Lustosa wrote: >I received a message from someone using outlook containing an >email attached (*.eml). Unfortunately, outlook sends the >attachment as "application/octet-stream", so mutt can't really >recognize it automatically. Then I open the message in mutt, hit >ctrl-e and change the type to "message/rfc822". What content-transfer-encoding was used for that body part? base64? In that case, the message which results from changing the content-type would violate applicable standards and mutt's expectations... Fixing this is, of course, possible, but would considerably complicate some code. -- Thomas Roessler<[EMAIL PROTECTED]> msg30859/pgp0.pgp Description: PGP signature
Trying to do too much with Mutt?
Greetings, fellow Mutterers. The problem is to: a) Archive outgoing mail to a local mail folder named in a header. b) Archive the same outgoing mail on a server, in similar fashion. The attempted solution so far is: a) my_hdr Fcc: default_project_name b) my_hdr X-Topic: default_project_name my_hdr Bcc: maildist@server Where maildist on the server has a procmail rule to handle archiving for any project present in the projects directory. OK, this works for the default case, but only 70-80% of my outgoing mail relates to default_project_name. To switch both local and remote archives, it is necessary to edit two headers. (It's not the labour that's objectionable, but the risk of forgetting to change one of them.) It is because the Fcc header is stripped from the sent email, that I resort to the second header. That leaves me trying to figure out how to do a file copy on X-Topic, if that is remotely possible. Alternatively, I don't suppose it's possible to use send-hook to put the outgoing mail through awk, to generate X-Topic from Fcc, before it is scrubbed? Now that would allow me to go to town! Regards, Erik
Re: mutt + procmail + qmail
* "Michael P. Soulier" <[EMAIL PROTECTED]> [020911 01:58]: > Can I see a filtering example from your .procmailrc? > Say, to filter this mailing list? * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 05:46]: > No, because the address subscribed to this list is johan-mutt and I have > > #cat .qmail-mutt > ~/Maildir/.mutt/ > > That's a lot better that filtering based on some header... huh? since when does this list get distributed via "johan-mutt"? Sven
Re: Trying to do too much with Mutt?
* Erik Christiansen <[EMAIL PROTECTED]> [2002-09-11 09:37]: > The problem is to: > a) Archive outgoing mail to a local mail folder named in a header. fcc-hook > b) Archive the same outgoing mail on a server, in similar fashion. Bcc > The attempted solution so far is: > a) my_hdr Fcc: default_project_name use "+name" > b) my_hdr X-Topic: default_project_name >my_hdr Bcc: maildist@server > >Where maildist on the server has a procmail rule to handle >archiving for any project present in the projects directory. > > OK, this works for the default case, but only 70-80% of my outgoing > mail relates to default_project_name. To switch both local > and remote archives, it is necessary to edit two headers. switch what? you are relating to *consequences* of a problem which you failed to describe properly. > (It's not the labour that's objectionable, but > the risk of forgetting to change one of them.) whatever. Sven
Re: mutt + procmail + qmail
* Sven Guckes <[EMAIL PROTECTED]> [020911 13:32]: > * "Michael P. Soulier" <[EMAIL PROTECTED]> [020911 01:58]: > > Can I see a filtering example from your .procmailrc? > > Say, to filter this mailing list? > * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 05:46]: > > No, because the address subscribed to this list is johan-mutt and I have > > #cat .qmail-mutt > > ~/Maildir/.mutt/ > > That's a lot better that filtering based on some header... > huh? since when does this list get distributed via "johan-mutt"? It doesn't. That's not what I'm saying either. What I'm saying is that the address I have subscribed to the list is [EMAIL PROTECTED], so list mail to me gets handled by my .qmail-mutt file. Thus, no need for filtering. HTC, -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: Sourcing scripts, screen flashes.
* Ryan Sorensen <[EMAIL PROTECTED]> [2002-09-10 06:32]: > Since I've added source lines for a couple scripts, when > I start up mutt, the screen flashes several times. > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"| > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"| > That sort of thing. source filename source filename| "filename foo" is *not a filename, i suppose. > Anything I can do to avoid this? rtfm?! Sven
Re: Compose macro question
* Pedro Alves <[EMAIL PROTECTED]> [2002-09-10 14:37]:
> On Tue, Sep 10, 2002 at 04:08:44PM +0200, Michael Tatge wrote:
> > Pedro Alves ([EMAIL PROTECTED]) muttered:
> > > I want to make a compose macro that verifies the from-address and changes
> > > the fcc according to that value...
> > >
> > > perhaps something like:
> > >
> > > compose V if ( == 'foo@bar' )then { = '=bla'}
> > >
> > > Can you give me a hand on this?
> >
> > What about fcc-hooks?
> >
> > Michael
>
> fcc hooks don't automatically update when I change from address. I change
> the from address often and I can't fill the configuration file with all the
> possible addresses. I'm not seeing other way..
whatever your macro to change your From: address is -
change it so it sources a setup file which
includes your headers and fcc-hooks.
Sven
Re: Changing attachment mime type
Thomas Roessler [[EMAIL PROTECTED]] wrote: > On 2002-09-10 10:40:46 -0300, Bruno Lustosa wrote: > > >I received a message from someone using outlook containing an > >email attached (*.eml). Unfortunately, outlook sends the > >attachment as "application/octet-stream", so mutt can't really > >recognize it automatically. Then I open the message in mutt, hit > >ctrl-e and change the type to "message/rfc822". > > What content-transfer-encoding was used for that body part? base64? > > In that case, the message which results from changing the > content-type would violate applicable standards and mutt's > expectations... Fixing this is, of course, possible, but would > considerably complicate some code. Text part (the message) is quoted-printable, attachment is base64, as you guessed. -- Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED] Network Administrator/Web Programmer | ICQ UIN: 1406477 Rio de Janeiro - Brazil | msg30866/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 10:11:22AM +1000, Iain Truskett wrote: > :0: > * ^Sender: owner-mutt-(dev|users)@mutt.org > apps-mutt/ the first line can actually be written as follows: :0 the second colon tells procmail to lock an mbox file which isn't necessary for maildir. -- Peter Abplanalp PGP: pgp.mit.edu msg30867/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: > * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 05:46]: > > No, because the address subscribed to this list is johan-mutt and I have > > > > #cat .qmail-mutt > > ~/Maildir/.mutt/ > > > > That's a lot better that filtering based on some header... > > huh? since when does this list get distributed via "johan-mutt"? he is talking about the qmail extension addresses. if you use qmail as your mta, you can create infinite extension addresses of the form -@domain which correspond to delivery instruction files of the form ~/.qmail-. for example, i might have an extension address for the foobar list which is [EMAIL PROTECTED] which corresponds to a ~/.qmail-foobar delivery instruction file much like the one above that tells qmail to drop the mail in my foobar maildir. it is a handy feature of qmail. -- Peter Abplanalp PGP: pgp.mit.edu msg30868/pgp0.pgp Description: PGP signature
Re: Trying to do too much with Mutt?
On Wed, Sep 11, 2002 at 07:33:23PM +1000, Erik Christiansen wrote: >Alternatively, I don't suppose it's possible to use send-hook to put >the outgoing mail through awk, to generate X-Topic from Fcc, before >it is scrubbed? Now that would allow me to go to town! i would suggest you create a sendmail wrapper that does whatever you want based on whatever header you set and then set sendmail = 'wrapper' in your muttrc. -- Peter Abplanalp PGP: pgp.mit.edu msg30869/pgp0.pgp Description: PGP signature
Re: mutt + procmail + qmail
* Peter T. Abplanalp <[EMAIL PROTECTED]> [2002-09-11 13:45]: > On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: > > * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 05:46]: > > > No, because the address subscribed to this list is johan-mutt and I have > > > > > > #cat .qmail-mutt > > > ~/Maildir/.mutt/ > > > > > > That's a lot better that filtering based on some header... > > > > huh? since when does this list get distributed via "johan-mutt"? > > he is talking about the qmail extension addresses. if you use qmail > as your mta, you can create infinite extension addresses of the form > -@domain which correspond to > delivery instruction files of the form ~/.qmail-. i know - but obviously i was under the impression that qmail would only use this when the address appears in the address lines (Cc:/To:) - but i was wrong there. i'd have looked it up - but those qmail man pages are not available on this system (or they moved.. whatever). > it is a handy feature of qmail. been using it for *years*. (check my webpages! :-) Sven
Re: mutt + procmail + qmail
On Wed, Sep 11, 2002 at 07:44:44AM -0600 or thereabouts, Peter T. Abplanalp wrote: > On Wed, Sep 11, 2002 at 01:32:19PM +0200, Sven Guckes wrote: qmail has totally eliminated the need for procmail on my mailserver by using .qmail files. Still use it after poping mail to my box, where Mutt reads it, althought I probably will be switching to maildir on that box too. Mutt is getting a little slow on opening the existing mboxs.. -- Best regards, Gary > > * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 05:46]: > > > #cat .qmail-mutt > > > ~/Maildir/.mutt/ > > > That's a lot better that filtering based on some header... > > > > huh? since when does this list get distributed via "johan-mutt"? > > he is talking about the qmail extension addresses. if you > use qmail as your mta, you can create infinite extension > addresses of the form -@domain which > which corresponds to a ~/.qmail-foobar delivery instruction > file much like the one above that tells qmail to drop the > mail in my foobar maildir. > it is a handy feature of qmail.
User-Agent: Mutt/1.5.1i
Folks,
is there a new release of mutt (1.5.1i) available?
wbr,
--lpr
Lukas Ruf Bellariastr. 11 CH-8002 Zuerich +41 1 2813545
http://www.lpr.chhttp://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
%L, %l in $status_format
Greetings. With no limit set, I would expect %L in $status_format to expand to either 0K (that's "zero-K", not "okay") or the full size of the mailbox (I do not know which of these behaviors is intended). Apparently it expands to both (finish reading before you remark please). When intially in a mailbox, implicitly with no limit set, %L == 0K. If the user sets the limit to ``.'' (translation: explicitly unsets the limit pattern, even though there already is none), %L then expands to the full mailbox size. It seems that %L doesn't know what it should do when there is no limit pattern. This a minor inconsistancy worked around by either %?L?%L&%l? or %?L?%L&0? depending on whether or not %L should be zero when there is no limit pattern. Inconsistent with what? %M. %M _always_ expands to the number of messages shown, regardless of whether there is a limit pattern or not. Using the string "%M/%L" in $status_format in a mailbox with 100 messages yields "100/0K". Ciao. Keith. -- "Isn't it time we care and lose the hate Understand our fears" -- Dream Theater, "Blind Faith"
Re: User-Agent: Mutt/1.5.1i
On Wed, Sep 11, 2002 at 04:20:41PM +0200, Lukas Ruf wrote: > is there a new release of mutt (1.5.1i) available? this is the cvs version. it hasn't been "released" afaik. -- Peter Abplanalp PGP: pgp.mit.edu msg30874/pgp0.pgp Description: PGP signature
Re: User-Agent: Mutt/1.5.1i
On Wed, 11 Sep 2002, Peter T. Abplanalp wrote:
> On Wed, Sep 11, 2002 at 04:20:41PM +0200, Lukas Ruf wrote:
> > is there a new release of mutt (1.5.1i) available?
>
> this is the cvs version. it hasn't been "released" afaik.
>
Do you consider it stable?
--lpr
--
Lukas Ruf Bellariastr. 11 CH-8002 Zuerich +41 1 2813545
http://www.lpr.chhttp://www.maremma.ch
http://www.{{topsy,nodeos}.net,{promethos,netbeast,rawip}.org}
Re: User-Agent: Mutt/1.5.1i
* Lukas Ruf <[EMAIL PROTECTED]> [2002-09-11 14:36]: > On Wed, 11 Sep 2002, Peter T. Abplanalp wrote: > > On Wed, Sep 11, 2002 at 04:20:41PM +0200, Lukas Ruf wrote: > > > is there a new release of mutt (1.5.1i) available? > > this is the cvs version. it hasn't been "released" afaik. > Do you consider it stable? if it was then it'd get released as 1.6 - see? ;-) bottom line: use cvs - or wait for 1.6 to be released. Sven
Re: User-Agent: Mutt/1.5.1i
On Wed, 11 Sep 2002, Sven Guckes wrote: > bottom line: use cvs - or wait for 1.6 to be released. > Ok, got the point, mutt follows a numbering scheme similar to Linux'? Thanks, --lpr
Re: Sourcing scripts, screen flashes.
On Wed, Sep 11, 2002 at 01:56:39PM +0200, Sven Guckes wrote:
> * Ryan Sorensen <[EMAIL PROTECTED]> [2002-09-10 06:32]:
> > Since I've added source lines for a couple scripts, when
> > I start up mutt, the screen flashes several times.
> > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"|
> > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"|
> > That sort of thing.
>
> source filename
> source filename|
>
> "filename foo" is *not a filename, i suppose.
Hi Sven - I'm trying to understand what you meant by this.
I'm guessing here - but does the vertical bar have to come at the
end of the script name ? Not at the end of the command line ?
Or does the sourced file have to limnit itself to mutt commands?
(I assume from the .sh ending of Ryan's files that the files being
sourced are shell scripts)
Or should Ryan be trying a wrapper script to encapsulate the
logic above ? something like :
source ~/mywrapper!
== example file "mywapper" =
#!/bin/sh
~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/
~/.mutt/hooks/folder.recip.sh ~/.Mail/people/
end file =
Sometimes even reading the manual is not sufficient. The admirable
terseness of UNIX/Linux documentation sometimes cause gaps in
understanding which are not apparent to those who are already familiar
with the topics being examined. I believe this is one of those times.
(I still prefer this to the "step by step robot" instructions that
are frequently passed off as documentation by some publishers.)
("click this, now click that, select from a list. etc... ")
>
> > Anything I can do to avoid this?
>
> rtfm?!
Which part of the manual would explain this please ?
I'm asking because I grepped the manual and I can't find anything about
how sourcing a file would cause screen flashes. The only other thing
I can think of would be that a command in Ryan's scripts somehow invoke
the clear/redraw screen function (^L) in mutt.
--
( Memoriam )
;===;()
# # # #::
# # # #::
# # # #::
# # # #::
# # # # # # #
# # # # # # #
# # # # # # #
# # # # # # #
# # # # # # #
# # # # # # #
For all the victims from over one hundred
countries who died one year ago today.
Re: Sourcing scripts, screen flashes.
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [11-09-2002 16:57]: > On Wed, Sep 11, 2002 at 01:56:39PM +0200, Sven Guckes wrote: > > * Ryan Sorensen <[EMAIL PROTECTED]> [2002-09-10 06:32]: > > > Since I've added source lines for a couple scripts, when > > > I start up mutt, the screen flashes several times. > > > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"| > > > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"| > > > That sort of thing. > > > > source filename > > source filename| > > > > "filename foo" is *not a filename, i suppose. > > Hi Sven - I'm trying to understand what you meant by this. > I'm guessing here - but does the vertical bar have to come at the > end of the script name ? Not at the end of the command line ? man muttrc /source source takes one argument, which should be a file. -- René Clerc - ([EMAIL PROTECTED]) No woman, no cry. -Bob Marley msg30879/pgp0.pgp Description: PGP signature
Re: Sourcing scripts, screen flashes.
* Ryan Sorensen <[EMAIL PROTECTED]> [2002-09-10 06:32]:
> source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"|
> source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"|
* Sven Guckes wrote:
> source filename
> source filename|
> "filename foo" is *not* a filename, i suppose.
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2002-09-11 14:57]:
> Hi Sven - I'm trying to understand what you meant by this.
> I'm guessing here - but does the vertical bar have to come at the
> end of the script name ? Not at the end of the command line ?
"filename" stands for the name of a file. no more - no less.
so - is "foo bar" a filename? or more specifically -
is there a file named "folder.recip.sh ~/.Mail/lists/"
(note the space!) in Ryan's ~/.mutt/hooks directory?
my guess is that this *file* does *not* exist.
> Sometimes even reading the manual is not sufficient.
yep - understanding it is required, too. *ehem*
> The admirable terseness of UNIX/Linux documentation sometimes
> cause gaps in understanding which are not apparent to those
> who are already familiar with the topics being examined.
> I believe this is one of those times.
au contraire. Ryan probably expected that he can use
any kind of commmand with parameters in this value.
and that's where he would be wrong because the
parameter is explicitly described as a *filename*.
or does it say "put parameters here" anywhere?
exactly.
> (I still prefer this to the "step by step robot" instructions that
> are frequently passed off as documentation by some publishers.)
> ("click this, now click that, select from a list. etc... ")
"mutt for dummies" includes all the manuals with examples -
these are 42 volumes if printed out and available
for just some bucks to get you a linux.
> > > Anything I can do to avoid this?
> > rtfm?!
> Which part of the manual would explain this please ?
the part which says "Usage: source filename"
yes, it is terse. but read on - there
are more sentences and even an example!
For example:
source /usr/local/share/Mutt.aliases
source ~/.mail_aliases
and well, if this is not clear now
then, um, get the windows version.
> I'm asking because I grepped the manual and I can't find
> anything about how sourcing a file would cause screen flashes.
error -> beep -> visual bell (aka flash).
> --
>( Memoriam )
> ;===;()
> # # # #::
> # # # #::
> # # # #::
> # # # #::
> # # # # # # #
> # # # # # # #
> # # # # # # #
> # # # # # # #
> # # # # # # #
> # # # # # # #
>
> For all the victims from over one hundred
> countries who died one year ago today.
the worst part about "9/11" is the reference
to the Eternal September and its signatures.
Osama is going to rot in /dev/null for that!
Sven
--
___ground_zero_
Re: User-Agent: Mutt/1.5.1i
* On 2002.09.11, in <[EMAIL PROTECTED]>, * "Lukas Ruf" <[EMAIL PROTECTED]> wrote: > On Wed, 11 Sep 2002, Sven Guckes wrote: > > > bottom line: use cvs - or wait for 1.6 to be released. > > > > Ok, got the point, mutt follows a numbering scheme similar to Linux'? Yes. I'm not sure why all the ruckus about cvs and the connotations of the word "release". There's a 1.5.1 tarball at ftp://ftp.mutt.org/mutt/devel/mutt-1.5.1i.tar.gz, just like the devel snapshots have always been. You're allowed to check out CVS snapshots if you like, but you can take advantage of periodic devel releases without it. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
Re: Sourcing scripts, screen flashes.
* Sven Guckes <[EMAIL PROTECTED]> [020911 17:23]: > * Ryan Sorensen <[EMAIL PROTECTED]> [2002-09-10 06:32]: > > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/lists/"| > > source "~/.mutt/hooks/folder.recip.sh ~/.Mail/people/"| > * Sven Guckes wrote: > > source filename > > source filename| > > "filename foo" is *not* a filename, i suppose. > "filename" stands for the name of a file. no more - no less. > so - is "foo bar" a filename? or more specifically - > is there a file named "folder.recip.sh ~/.Mail/lists/" > (note the space!) in Ryan's ~/.mutt/hooks directory? > my guess is that this *file* does *not* exist. Sorry Sven, but I can't confirm what you're saying. If I enter source 'echo "alias foobar <[EMAIL PROTECTED]>"'| at mutts : prompt, the screen will "flash". But the alias (that wasn't defined before...) will work, too! It seems to be the same screen "flash" that would occur on entering !chmod 644 public_html/test.txt (i e running a program from within mutt that doesn't give any stdout to display, either because there is none or because mutt uses it internally...) Regards, -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: Sourcing scripts, screen flashes.
* On 2002.09.11, in <[EMAIL PROTECTED]>, * "Sven Dogbert Guckes" <[EMAIL PROTECTED]> wrote: > > "filename" stands for the name of a file. no more - no less. Wrong, Sven. > > Sometimes even reading the manual is not sufficient. > > yep - understanding it is required, too. *ehem* Indeed. So why are you talking? > > The admirable terseness of UNIX/Linux documentation sometimes > > cause gaps in understanding which are not apparent to those > > who are already familiar with the topics being examined. > > I believe this is one of those times. > > au contraire. Ryan probably expected that he can use > any kind of commmand with parameters in this value. > and that's where he would be wrong because the > parameter is explicitly described as a *filename*. > or does it say "put parameters here" anywhere? > exactly. Wrong, Sven. Ryan probably did not expect that he can use any kind of command here, but we'd have to ask him, and it's not worth speculating about. The fact is that a "filename" argument, in mutt, is allowed to be either a filename, or an "abbreviation" for a filename (!, =foo, ~/foo, etc.), or a pipe. Yes, a pipe, Sven. Try it before spouting sometime. > and well, if this is not clear now > then, um, get the windows version. Do you take your own advice, Sven? Ryan: The pipe symbol needs to be inside the quotation marks, but it's not allowed to take arguments. source "~/.mutt/hooks/folder.recip.lists.sh |" source "~/.mutt/hooks/folder.recip.people.sh |" These could theoretically be symlinked to the same script, and figure out what to do by examining $0. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
Re: Sourcing scripts, screen flashes.
* Johan Almqvist <[EMAIL PROTECTED]> [2002-09-11 15:52]: > :source 'echo "alias foobar <[EMAIL PROTECTED]>"'| > the screen will "flash". But the alias > (that wasn't defined before) will work, too! aha - so the pipe symbol at the end forces an evaluation.. hmm.. $ cat /tmp/test echo 'set signature=/etc/passwd' echo 'set pager="vim -"' $ mutt :source /tmp/test| ok - mutt flashes but it does execute the set commands. now, how to have all this executed silently? Sven [thinking about recursion, too, but...]
Re: Sourcing scripts, screen flashes.
* David Champion <[EMAIL PROTECTED]> [2002-09-11 16:09]: > The pipe symbol needs to be inside the quotation > marks, but it's not allowed to take arguments. > source "~/.mutt/hooks/folder.recip.lists.sh |" > source "~/.mutt/hooks/folder.recip.people.sh |" why use quotation marks at all then? "source file|" suffices, doesn't it? Sven
calling an external command from send-hook
Morning, I'm trying to get mutt to call an external command from a send-hook like in the following muttrc line: send-hook . '!sched.log Testing send hook\n' but it always just says "!sched.log command not found" after setting to and subject from a message. Is it possible to use ! in a send hook, or only just in macros (which i've gotten to work just fine). burton msg30886/pgp0.pgp Description: PGP signature
Re: Sourcing scripts, screen flashes.
* David Champion <[EMAIL PROTECTED]> [020911 18:08]: > Ryan: > The pipe symbol needs to be inside the quotation marks, but it's not > allowed to take arguments. What no arguments? Worked fine for me - see previous mail. -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: top-post supports bad software (was: location of signature.)
On Fri, Sep 06, 2002 at 01:54:38PM +0200, Sven Guckes wrote: > > BTW, why did this post show up in my inbox rather than in my > > mutt folder? My procmailrc searches for "^TO.*mutt-users".. > > please explain why you use ".*" here. Because whoever's procmailrc I copied when I was first learning procmail didn't know how to use procmail. I have since learned that there are procmailrc and procmailex man pages and they contain much better samples than 99% of what's out there on the 'net. Thanks for the procmail tips in the other posts; I'll spend some time playing with them. Paul
mutt 1.4 not displaying headers or body in pager
I tried to upgrade from mutt 1.2.5 to 1.4 this morning, but when I started mutt after the upgrade, I could see the subjects all the emails in my inbox in the viewer, but when I try to view one of the emails, all I got was a blank page. Using 'e' to edit the email pulled the entire email correctly into vi. The text was not simply invisible, as I could not cut-and-paste it from my xterm. Removing the colors from my muttrc did not help. Is there a setting I am missing somewhere? Thanks, Paul
Re: mutt 1.4 not displaying headers or body in pager
Paul Brannan wrote: > I tried to upgrade from mutt 1.2.5 to 1.4 this morning, but when I > started mutt after the upgrade, I could see the subjects all the emails > in my inbox in the viewer, but when I try to view one of the emails, all > I got was a blank page. Using 'e' to edit the email pulled the entire > email correctly into vi. The text was not simply invisible, as I could > not cut-and-paste it from my xterm. Removing the colors from my muttrc > did not help. Try running Mutt with no configuration files at all (mutt -n -F /dev/null) and see if you still have the problem.
Re: Sourcing scripts, screen flashes.
* On 2002.09.11, in <[EMAIL PROTECTED]>, * "Johan Almqvist" <[EMAIL PROTECTED]> wrote: > * David Champion <[EMAIL PROTECTED]> [020911 18:08]: > > Ryan: > > The pipe symbol needs to be inside the quotation marks, but it's not > > allowed to take arguments. > > What no arguments? Worked fine for me - see previous mail. I've tried this in the past (with args), and ran into trouble, concluding that arguments didn't work for "source". (This was when I changed my muttrc to call m4 as a preprocessor on my real muttrc, as some might recall.) But you're certainly right; it works now. Maybe this was changed in a patch, or maybe I diagnosed my problem incorrectly back whenever. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
Re: User-Agent: Mutt/1.5.1i
Hi, all -- ...and then David Champion said... % ... % of the word "release". There's a 1.5.1 tarball at % ftp://ftp.mutt.org/mutt/devel/mutt-1.5.1i.tar.gz, just like the devel YAY! YIPPEE! WONDERFUL! Good deal. HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg30892/pgp0.pgp Description: PGP signature
Re: Sourcing scripts, screen flashes.
* David Champion <[EMAIL PROTECTED]> [2002-09-11 15:22]: > (This was when I changed my muttrc to call m4 as a preprocessor on my > real muttrc, as some might recall.) I recall this, and also recall a promise to post said m4 config to the list, so we could see what it looked like... (darren) -- The language Unix is vastly more inconsistent than the language Perl. And guaranteed to remain that way, forever and ever, amen. -- Larry Wall
Re: calling an external command from send-hook
* Burton Samograd <[EMAIL PROTECTED]> [2002-09-11 16:55]: > I'm trying to get mutt to call an external command > from a send-hook like in the following muttrc line: > send-hook . '!sched.log Testing send hook\n' > > but it always just says "!sched.log command not found" after setting > to and subject from a message. have you tried by calling the script with its full path, ie with "!/path/script foo bar"? this *ought* to work! Sven
Re: calling an external command from send-hook
> have you tried by calling the script with its > full path, ie with "!/path/script foo bar"? > this *ought* to work! i've tried a number of variations with path and other commands (like "!echo Testing > ~/mutt.log" ) and i keep getting the unknown command error :-/ i know this *should* work but that doesn't seem to be the case at the moment (i'm using mutt cvs so maybe a bug was intoduced?). burton msg30895/pgp0.pgp Description: PGP signature
Re: calling an external command from send-hook
Sven Guckes wrote: > * Burton Samograd <[EMAIL PROTECTED]> [2002-09-11 16:55]: > > I'm trying to get mutt to call an external command > > from a send-hook like in the following muttrc line: > > send-hook . '!sched.log Testing send hook\n' > > > > but it always just says "!sched.log command not found" after setting > > to and subject from a message. > > have you tried by calling the script with its > full path, ie with "!/path/script foo bar"? > this *ought* to work! No, it won't. send-hook only allows you to execute configuration commands, like you would put in a muttrc. What he's trying to do is execute one of Mutt's interactive functions. There is no "exec" configuration command which allows you to run an external program.
Re: Sourcing scripts, screen flashes.
David -- ...and then darren chamberlain said... % % * David Champion <[EMAIL PROTECTED]> [2002-09-11 15:22]: % > (This was when I changed my muttrc to call m4 as a preprocessor on my % > real muttrc, as some might recall.) % % I recall this, and also recall a promise to post said m4 config to the % list, so we could see what it looked like... Same here! Is it ready *yet*? ;-) TIA & HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg30897/pgp0.pgp Description: PGP signature
Re: calling an external command from send-hook
> > No, it won't. send-hook only allows you to execute configuration > commands, like you would put in a muttrc. What he's trying to do is > execute one of Mutt's interactive functions. There is no "exec" > configuration command which allows you to run an external program. Ah, i thought that might be the problem. Would there be any way of actually doing what i'm trying to do? Maybe setting up a macro and then calling that from send-hook? burton msg30898/pgp0.pgp Description: PGP signature
Re: calling an external command from send-hook
* On 2002.09.11, in <[EMAIL PROTECTED]>, * "Michael Elkins" <[EMAIL PROTECTED]> wrote: > > No, it won't. send-hook only allows you to execute configuration > commands, like you would put in a muttrc. What he's trying to do is > execute one of Mutt's interactive functions. There is no "exec" > configuration command which allows you to run an external program. You can play tricks, though. For instance: send-hook . 'source "sched.log.sh Testing send hook|"' sched.log.sh #!/bin/sh ## Any stdout will be parsed by mutt as configuration commands sched.log "$@" >/dev/null 2>&1 sched.log.sh I haven't tried this particular example, but the principle should be sound. You can use this to make/modify the hooks on the fly, too. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
sending as who you've been addressed as.
Hi, I have several email aliases that I use frequently, when I reply to an email, i'd like to send as whoever the email was addressed to, automatically. How can I do this? Also, when I send to certain email addresses (specifically mailing lists, etc) I'd like to use a specific email alias as well, how can I do this? I've been messing with 'send-hook' but it seems like no matter what I change, it just doesn't work. Thanks for your help. - nick
Re: calling an external command from send-hook
Burton Samograd wrote: > Ah, i thought that might be the problem. Would there be any way of > actually doing what i'm trying to do? Maybe setting up a macro and > then calling that from send-hook? You could try to use the push command to simulate keystrokes, but that won't be executed until the next time mutt asks for input from the user, not the point at which the send-hook is executed. For instance, if you have "set autoedit edit_hdrs", the macro you want to call would not be executed until *after* you edited the message with the external editor, when you have returned to the compose menu. There is no way to get the command to execute at the time the send-hook is executed. Well, that's not technically true. If you have a backtic command in a send-hook, it does get executed. You could make a script which emits a harmless muttrc command (like "unignore nonexistent") and use something like: send-hook . '`side_effect`' where side_effect is a script like: #!/bin/sh # run a command, redirect output to /dev/null ... > /dev/null 2>&1 # return dummy command to Mutt for execution echo unignore nonexistent A bit of a hack, but it will allow you do what you want.
Re: sending as who you've been addressed as.
Nick Jennings wrote: > I have several email aliases that I use frequently, when I reply to an > email, i'd like to send as whoever the email was addressed to, automatically. > How can I do this? see $reverse_name in the mutt manual.
Re: calling an external command from send-hook
Alas! Burton Samograd spake thus: > > > > No, it won't. send-hook only allows you to execute configuration > > commands, like you would put in a muttrc. What he's trying to do is > > execute one of Mutt's interactive functions. There is no "exec" > > configuration command which allows you to run an external program. > > Ah, i thought that might be the problem. Would there be any way of > actually doing what i'm trying to do? Maybe setting up a macro and > then calling that from send-hook? Uh, push? Untested WAG: send-hook 'push !whatever...' -- Rob 'Feztaa' Park http://members.shaw.ca/feztaa/ -- You will be aided greatly by a person whom you thought to be unimportant. msg30903/pgp0.pgp Description: PGP signature
getting from and subject in send-hook
Hi again, Now that my first problem is soved (calling my command from a send-hook) now I'm running into the second part of what i'm trying to do. Is there any way to access the To: and Subject: from the message that is begin set? I've already set them before the hook is called, so i'm thinking there might be some way, but of course, i could be wrong. :) burton msg30904/pgp0.pgp Description: PGP signature
make install error
I get the following error during 'make install' and I don't understand. make[1]: *** No rule to make target mime.h', needed by ttach.o'. Stop. make[1]: Leaving directory /mnt/scratch/KeeP/mutt-1.5.1' make: *** [install-recursive] Error 1 Any help will be appreciated. -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org
[PATCH] display-subject
The attached patch copies the functionality of the display-address function
to display the message subject, by default bound to S. This is useful if
your term isn't infinitely wide and/or you have a crowded $index_format.
I've been using a version of this since 1.3.2x without any problems; it's
pretty much just a copy of the display-address stuff so it should be pretty
innocuous.
diff -dupr mutt-cvs.orig/PATCHES mutt-cvs/PATCHES
--- mutt-cvs.orig/PATCHES Wed Sep 11 23:05:23 2002
+++ mutt-cvs/PATCHESWed Sep 11 23:26:04 2002
@@ -0,0 +1 @@
+patch-1.5.jjb.display_subject.1
diff -dupr mutt-cvs.orig/OPS mutt-cvs/OPS
--- mutt-cvs.orig/OPS Wed Sep 11 23:05:23 2002
+++ mutt-cvs/OPSWed Sep 11 23:26:04 2002
@@ -53,6 +53,7 @@ OP_DELETE_MAILBOX "delete the current ma
OP_DELETE_SUBTHREAD "delete all messages in subthread"
OP_DELETE_THREAD "delete all messages in thread"
OP_DISPLAY_ADDRESS "display full address of sender"
+OP_DISPLAY_SUBJECT "display full subject of message"
OP_DISPLAY_HEADERS "display message and toggle header weeding"
OP_DISPLAY_MESSAGE "display a message"
OP_EDIT_MESSAGE "edit the raw message"
diff -dupr mutt-cvs.orig/PATCHES mutt-cvs/PATCHES
--- mutt-cvs.orig/PATCHES Thu Jan 24 06:10:47 2002
+++ mutt-cvs/PATCHESWed Sep 11 23:26:04 2002
@@ -0,0 +1 @@
+patch-1.3.25.jjb.display_subject.1
diff -dupr mutt-cvs.orig/commands.c mutt-cvs/commands.c
--- mutt-cvs.orig/commands.cSat Apr 20 12:30:38 2002
+++ mutt-cvs/commands.c Wed Sep 11 23:26:04 2002
@@ -619,6 +619,11 @@ void mutt_display_address (ENVELOPE *env
mutt_message ("%s: %s", pfx, buf);
}
+void mutt_display_subject (ENVELOPE *env)
+{
+ mutt_message ("Subject: %s", env->subject);
+}
+
static void set_copy_flags (HEADER *hdr, int decode, int decrypt, int *cmflags, int
*chflags)
{
*cmflags = 0;
diff -dupr mutt-cvs.orig/curs_main.c mutt-cvs/curs_main.c
--- mutt-cvs.orig/curs_main.c Wed Sep 11 23:05:23 2002
+++ mutt-cvs/curs_main.cWed Sep 11 23:26:04 2002
@@ -1687,8 +1687,15 @@ int mutt_index_menu (void)
case OP_DISPLAY_ADDRESS:
CHECK_MSGCOUNT;
-CHECK_VISIBLE;
+ CHECK_VISIBLE;
mutt_display_address (CURHDR->env);
+ break;
+
+ case OP_DISPLAY_SUBJECT:
+
+ CHECK_MSGCOUNT;
+ CHECK_VISIBLE;
+ mutt_display_subject (CURHDR->env);
break;
case OP_ENTER_COMMAND:
diff -dupr mutt-cvs.orig/doc/manual.sgml.tail mutt-cvs/doc/manual.sgml.tail
--- mutt-cvs.orig/doc/manual.sgml.tail Fri Jun 14 08:17:22 2002
+++ mutt-cvs/doc/manual.sgml.tail Wed Sep 11 23:26:04 2002
@@ -62,6 +62,7 @@ delete-pattern D delete me
delete-subthread ESC d delete all messages in subthread
delete-thread ^D delete all messages in thread
display-address@ display full address of sender
+display-subjectS display full subject of message
display-toggle-weedh display message and toggle header weeding
display-message RET display a message
edit e edit the current message
@@ -132,6 +133,7 @@ delete-message d delete th
delete-subthread ESC d delete all messages in subthread
delete-thread ^D delete all messages in thread
display-address@ display full address of sender
+display-subjectS display full subject of message
display-toggle-weedh display message and toggle header weeding
edit e edit the current message
edit-type ^E edit the current message's Content-Type
diff -dupr mutt-cvs.orig/functions.h mutt-cvs/functions.h
--- mutt-cvs.orig/functions.h Wed Sep 11 23:05:23 2002
+++ mutt-cvs/functions.hWed Sep 11 23:26:04 2002
@@ -128,6 +128,7 @@ struct binding_t OpMain[] = {
{ "buffy-list", OP_BUFFY_LIST, "." },
{ "sync-mailbox",OP_MAIN_SYNC_FOLDER,"$" },
{ "display-address", OP_DISPLAY_ADDRESS, "@" },
+ { "display-subject", OP_DISPLAY_SUBJECT, "S" },
{ "pipe-message",OP_PIPE,"|" },
{ "next-new",OP_MAIN_NEXT_NEW, "\t" },
{ "previous-new",OP_MAIN_PREV_NEW, "\033\t" },
@@ -204,6 +205,7 @@ struct binding_t OpPager[] = {
{ "show-version",OP_VERSION, "V" },
{ "search-toggle", OP_SEARCH_TOGGLE, "\\" },
{ "display-address", OP_DISPLAY_ADDRESS, "@" },
+ { "display-subject", OP_DISPLAY_SUBJECT, "S" },
{ "next-new",OP_MAIN_NEXT_NEW, "\t" },
{ "pipe-message",OP_PIPE,"|" },
{ "help",OP_HELP,"?" },
diff -dupr mutt-cvs.orig/pager.c mutt-cvs/pager.c
--- mutt-cvs.orig/pager.c Wed Sep 11 23:05:24 2002
+++ mutt-cvs/pager.cWed Sep 11 23:26:04 2
