-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, August 26 at 11:46 PM, quoth Shreevatsa R:
>> Skip the escaping, and just use quotes:
>>
>> mutt -e "push '~i "$MID"'" $@
>>
>> AFAIK quote characters aren't allowed in Message-IDs.
>
> That's probably true, but quotes don't work. Start
On Tue, Aug 26, 2008 at 10:35 PM, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday, August 26 at 10:32 PM, quoth Shreevatsa R:
>> On Sun, Aug 24, 2008 at 7:24 PM, Christian Ebert <[EMAIL PROTECTED]> wrote:
>>> * Kyle Wheeler on Sunday, August
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, August 26 at 10:32 PM, quoth Shreevatsa R:
> On Sun, Aug 24, 2008 at 7:24 PM, Christian Ebert <[EMAIL PROTECTED]> wrote:
>> * Kyle Wheeler on Sunday, August 24, 2008 at 16:41:53 -0500
>>> function reply() {
>>> MID=$1; shift;
>>
On Sun, Aug 24, 2008 at 7:24 PM, Christian Ebert <[EMAIL PROTECTED]> wrote:
> * Kyle Wheeler on Sunday, August 24, 2008 at 16:41:53 -0500
>> function reply() {
>> MID=$1; shift;
> mutt -e "push '~i $MID'" $@
>> }
Thanks, everyone. One minor annoyance is when Message-IDs have special
charac
* Kyle Wheeler <[EMAIL PROTECTED]> [08-26-08 13:55]:
>
> A folder-hook? Hmmm...
>
> source "awk '{print \"folder-hook . \\\"~h References:
> \\\",$1}'|"
>
> Just a thought, anyway. Seems a bit excessive, though. Much easier to
> just have your MDA delete those messages, rather than have m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, August 26 at 05:41 PM, quoth Marianne Promberger:
> Is it possible to extract a specific message header from mutt and pass
> it on to a shell command?
Not really, but there are ways of getting around that.
> maybe by passing the current
Is it possible to extract a specific message header from mutt and pass
it on to a shell command? maybe by passing the current message to
formail (but then, what would I write for "the current message" on
mutt's shell command prompt that comes up when I press "!" ?)
Background:
I'd like to be able
Hi,
* Kyle Wheeler wrote:
Second, since mutt already knows about List-Post to reply to a list
list even without a "subscribe" or "list" command, it should be
taught how to detect mailing lists completely. That way only mailing
lists without a given set of headers would require "list" commands
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, August 26 at 04:57 PM, quoth Rocco Rutte:
> First, at least one mailing lists considers setting Mail-Followup-To
> headers to achieve exactly that (no duplicate messages) being
> "rude", e.g. http://marc.info/?l=git&m=121218565402351&w=2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, August 26 at 09:44 PM, quoth bill lam:
>Hi All,
>Sometime mutt hangs or waits for a long time during downloading or
>uploading mail. Is there any method to interrupt other than killall?
There's no way to interrupt that doesn't kill mutt;
Hi,
* bill lam wrote:
Sometime mutt hangs or waits for a long time during downloading or
uploading mail. Is there any method to interrupt other than killall?
Is there progress in the mean time? How long does it take? Can you
exclude networking problems of any kind?
Currently there's no wa
Hi,
* Kyle Wheeler wrote:
Well, without them, you can't use patterns like ~l or ~u. Also, without
them, mutt doesn't set the Mail-Followup-To header properly (which
helps avoid receiving duplicate responses due to people responding to
"all" and thus sending to both the list and to you). Also
Hi All,
Sometime mutt hangs or waits for a long time during downloading or
uploading mail. Is there any method to interrupt other than killall?
--
regards,
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
On Sat, Aug 23, 2008 at 11:57:13AM -0500, Kyle Wheeler wrote:
> On Saturday, August 23 at 08:46 PM, quoth Chris Bannister:
> > Is there anything wrong with NOT having a "subscribe" command for
> > any mailing lists you are subscribed to in your .muttrc?
>
> Well, without them, you can't use patte
14 matches
Mail list logo
