| knowledge-database (beta) |
 |
Current group: comp.mail.mutt
Saving tagged messages _usually_, but not always, works?
| s. keeling | | Sven Guckes | | s. keeling | | Sven Guckes | | s. keeling | | Sven Guckes |
|
|
| | From: | s. keeling | | Subject: | Saving tagged messages _usually_, but not always, works? | | Date: | 8 Jan 2005 17:37:03 GMT |
|
|
 | This is my second attempt to clear this up. I tried what Sven
suggested the last time (RTFM), and that didn't help.
In my .muttrc, I have:
folder-hook IN.debian-security 'save-hook . =debian-security'
folder-hook IN.debian-security-announce 'save-hook . =debian-security'
The first one works fine. Trying to use the second one, however,
results in mutt prompting me:
Save tagged to mailbox:
Where is mutt getting that from, and why?
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling Linux Counter #80292
- - http://www.ietf.org/rfc/rfc1855.txt
Spammers! http://www.spots.ab.ca/~keeling/autospam.html
|
|
| | From: | Sven Guckes | | Subject: | Re: Saving tagged messages _usually_, but not always, works? | | Date: | 8 Jan 2005 18:56:56 GMT |
|
|
| * s. keeling [2005-01-08]:
> This is my second attempt to clear this up. I tried what
> Sven suggested the last time (RTFM), and that didn't help.
>
> In my .muttrc, I have:
>
> folder-hook IN.debian-security 'save-hook . =debian-security'
> folder-hook IN.debian-security-announce 'save-hook . =debian-security'
>
> The first one works fine. Trying to use the
> second one, however, results in mutt prompting me:
>
> Save tagged to mailbox:
>
> Where is mutt getting that from, and why?
do we really have to point out that the reader
has to deal with an unknown vesion of mutt and with
an inclomplete setup so only guesses *might* work?
rtf bug reporting guide.
Sven
|
|
| | From: | s. keeling | | Subject: | Re: Saving tagged messages _usually_, but not always, works? | | Date: | 9 Jan 2005 19:08:19 GMT |
|
|
| Sven Guckes :
> * s. keeling [2005-01-08]:
> >
> > In my .muttrc, I have:
> >
> > folder-hook IN.debian-security 'save-hook . =debian-security'
> > folder-hook IN.debian-security-announce 'save-hook . =debian-security'
> >
> > The first one works fine. Trying to use the
> > second one, however, results in mutt prompting me:
> >
> > Save tagged to mailbox:
> >
> > Where is mutt getting that from, and why?
>
> do we really have to point out that the reader
> has to deal with an unknown vesion of mutt and with
Good point. Sorry. 1.3.28-2.2 from Debian stable
> an inclomplete setup so only guesses *might* work?
What more do you want to know?
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling Linux Counter #80292
- - http://www.ietf.org/rfc/rfc1855.txt
Spammers! http://www.spots.ab.ca/~keeling/autospam.html
|
|
| | From: | Sven Guckes | | Subject: | Re: Saving tagged messages _usually_, but not always, works? | | Date: | 10 Jan 2005 02:53:23 GMT |
|
|
| * s. keeling [2005-01-09]:
> Sven Guckes :
>> * s. keeling [2005-01-08]:
>> > [mutt 1.3.28-2.2 from debian stable]
>> > In my .muttrc, I have:
>> >
>> > folder-hook IN.debian-security 'save-hook . =debian-security'
>> > folder-hook IN.debian-security-announce 'save-hook . =debian-security'
>> >
>> > The first one works fine. Trying to use the
>> > second one, however, results in mutt prompting me:
>> >
>> > Save tagged to mailbox:
>> >
>> > Where is mutt getting that from, and why?
>> do we really have to point out that the reader
>> has to deal with an unknown vesion of mutt and with
>> an inclomplete setup so only guesses *might* work?
>
> What more do you want to know?
other options values ($record, $save-name)
and the rest of all other interfering hooks?!
if in doubt then post the url of the setup.
anyway, my mutt 1.5.6 doesnt do this.
ever considered upgrading?
Sven
|
|
| | From: | s. keeling | | Subject: | Re: Saving tagged messages _usually_, but not always, works? | | Date: | 22 Jan 2005 20:59:42 GMT |
|
|
| Sven Guckes :
> * s. keeling [2005-01-09]:
> > Sven Guckes :
> >> * s. keeling [2005-01-08]:
> >> > [mutt 1.3.28-2.2 from debian stable]
> >> > In my .muttrc, I have:
> >> >
> >> > folder-hook IN.debian-security 'save-hook . =debian-security'
> >> > folder-hook IN.debian-security-announce 'save-hook . =debian-security'
> >> >
> >> > The first one works fine. Trying to use the
> >> > second one, however, results in mutt prompting me:
> >> >
> >> > Save tagged to mailbox:
>
> other options values ($record, $save-name)
set record=+sent
# unset save_name
Hmm ... Thanks. I'll look into those, and related.
> and the rest of all other interfering hooks?!
> if in doubt then post the url of the setup.
http://www.spots.ab.ca/~keeling/20050122_muttrc.html
> anyway, my mutt 1.5.6 doesnt do this.
> ever considered upgrading?
Only as a last resort. This is the version people get when they
install Debian stable. If it's broken, we owe it to them to find that
out, even if sarge is going stable RSN.
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.spots.ab.ca/~keeling Linux Counter #80292
- - http://www.ietf.org/rfc/rfc1855.txt
Spammers! http://www.spots.ab.ca/~keeling/autospam.html
|
|
| | From: | Sven Guckes | | Subject: | Re: Saving tagged messages _usually_, but not always, works? | | Date: | 22 Jan 2005 22:07:46 GMT |
|
|
| * s. keeling [2005-01-22]:
> Sven Guckes :
>> and the rest of all other interfering hooks?!
>> if in doubt then post the url of the setup.
> http://www.spots.ab.ca/~keeling/20050122_muttrc.html
still undecided as to whether to use reverse_alias and reverse_name?
"pip_split" - gotta love that one, even though it's commented out.
and wouldn't this shorten a rule?:
fcc-hook . /dev/null
the open + close hooks indicte that you are not
using the vanilla version but a patched one.
you know that this is not "mutt" anymore, right?
(comp.mail.mutt.patched, anyone?)
>> anyway, my mutt 1.5.6 doesnt do this.
>> ever considered upgrading?
>
> Only as a last resort. This is the version people get
> when they install Debian stable. If it's broken, we owe it
> to them to find that out, even if sarge is going stable RSN.
as if a version with known bugs is better than
a more recent version with some fixes. *sigh*
i'd rather give them the most recent version
and have a lot more potential "beta testers". ;-)
Sven
|
|
|
| | |
|
 |