; when I add "x-url" to the ignore. What gives?
Gary> Patterns are case-insensitive as long as they contain only
Gary> lower-case letters. If you include an upper-case letter in a
Gary> pattern, or include a range (e.g., [a-z]) that because of your
Gary> locale includes an
Ian Zimmerman wrote:
> The part of the documentation about the "ignore" command talks about
> "patterns". As far as I can see it never precisely says what kind of
> patterns these are - regexps, shell globs, fixed substrings, or what.
It's a case-independe
On 2015-05-27, Ian Zimmerman wrote:
> The part of the documentation about the "ignore" command talks about
> "patterns". As far as I can see it never precisely says what kind of
> patterns these are - regexps, shell globs, fixed substrings, or what.
Look in
The part of the documentation about the "ignore" command talks about
"patterns". As far as I can see it never precisely says what kind of
patterns these are - regexps, shell globs, fixed substrings, or what.
The reason I ask is I had "x-" as one of the patterns,
Hi Mikle,
On Fri, Apr 30, 2010 at 04:08:52PM +0400, Mikle Krutov wrote:
In the official docs there is probably some kind of error:
http://www.mutt.org/doc/manual/manual-3.html#ss3.8
To remove a previously added token from the list, use the ``unignore''
command. *Note that if you do
27;'
>command. *Note that if you do ``ignore x-'' it is not possible to
>``unignore x-mailer,'' for example.* The ``unignore'' command does not
>make Mutt display headers with the given pattern.
but:
>For example:
># Sven's draconian header weedin
I'm trying to get the ignore-thread patch to apply. I've tried both [1]
and [2], they fail in the same way.
This is what epatch (the function used in gentoo ebuilds to apply
patches) tries:
***** ignore-thread-1.5.18.patch *
==
PATCH COMMAND:
I'm testing whether posts to mutt-users are still generating
challenge-response messages.
I want to see *some* X-headers, like people's interesting and funny custom
my_hdrs (even though there doesn't seem to be as many of them these days).
But of course I don't want to see all X-headers.
So I have a very long list of boring and irrelevant X-headers in my
"ignore&q
Hi,
I'm looking for something like gmail's "mute" or the ignore-thread
patch shown on this page: http://wiki.mutt.org/?PatchList (the link
for ignore-thread seems to be dead, btw).
Did I miss something or is this not implemented?
Thanks,
--
Cristóbal Palmer
ibiblio.org systems administrator
--WhfpMioaduB5tiZL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Rocco Rutte spake thus:
> > he has to reboot every 3 hours to put on a kewl new linux kernel.
>=20
> It may sound funny, but I really saw some Linux guys ta
* Rocco Rutte <[EMAIL PROTECTED]> [2002-04-01 16:21]:
> On Mon, Apr 01, 2002 at 12:54:17:PM -0800 Will Yardley wrote:
> > Rocco Rutte wrote:
> >
> > > At least it was the smiley after your question which confused me. As I
> > > read you use a linux from scratch. Are you sure it looks professiona
Alas! Rocco Rutte spake thus:
> > I see... ;)
>
> At least it was the smiley after your question which confused me. As I
> read you use a linux from scratch. Are you sure it looks professional
> advertising uptimes of 1 or 2 hours? ;-)
If you use Windows regularly, 1 or 2 hours is plenty impress
* On 2002.04.01, in <[EMAIL PROTECTED]>,
* "Rocco Rutte" <[EMAIL PROTECTED]> wrote:
>
> It may sound funny, but I really saw some Linux guys talking about what
> would be necessary to replace a kernel 'on the fly'. Not that it does
> make lots of sence or is extraordinary usefull, but to so
begin quoting what Rocco Rutte said on Mon, Apr 01, 2002 at 11:20:32PM +0200:
>
> It may sound funny, but I really saw some Linux guys talking about what
> would be necessary to replace a kernel 'on the fly'. Not that it does
> make lots of sence or is extraordinary usefull, but to some of them
On Mon, Apr 01, 2002 at 11:20:32PM +0200, Rocco Rutte wrote:
> It may sound funny, but I really saw some Linux guys talking about what
> would be necessary to replace a kernel 'on the fly'. Not that it does
> make lots of sence or is extraordinary usefull, but to some of them
> uptime is all that
Hi,
On Mon, Apr 01, 2002 at 12:54:17:PM -0800 Will Yardley wrote:
> Rocco Rutte wrote:
>
> > At least it was the smiley after your question which confused me. As I
> > read you use a linux from scratch. Are you sure it looks professional
> > advertising uptimes of 1 or 2 hours? ;-)
>
> he has
Rocco Rutte wrote:
> At least it was the smiley after your question which confused me. As I
> read you use a linux from scratch. Are you sure it looks professional
> advertising uptimes of 1 or 2 hours? ;-)
he has to reboot every 3 hours to put on a kewl new linux kernel.
--
Will Yardley
inp
Hi,
On Wed, Mar 27, 2002 at 01:07:07:PM -0700 Rob 'Feztaa' Park wrote:
> Alas! Martin Karlsson spake thus:
> > Rob, your X-Uptime header shows even the no. of hundreds odf
> > seconds; I think Rocco ironically suggests that it perhaps could be
> > more specific -> meaning that he thinks it is _ve
Simon, et al --
...and then Simon White said...
%
% 27-Mar-02 at 13:07, Rob 'Feztaa' Park ([EMAIL PROTECTED]) wrote :
% > Alas! Martin Karlsson spake thus:
% > > Rob, your X-Uptime header shows even the no. of hundreds odf
% > > seconds; I think Rocco ironically suggests that it perhaps could be
27-Mar-02 at 13:07, Rob 'Feztaa' Park ([EMAIL PROTECTED]) wrote :
> Alas! Martin Karlsson spake thus:
> > Rob, your X-Uptime header shows even the no. of hundreds odf
> > seconds; I think Rocco ironically suggests that it perhaps could be
> > more specific -> meaning that he thinks it is _very_ sp
--6sX45UoQRIJXqkqR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Martin Karlsson spake thus:
> Rob, your X-Uptime header shows even the no. of hundreds odf
> seconds; I think Rocco ironically suggests that it perhaps coul
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-27 11.28 -0700]:
> Alas! Rocco Rutte spake thus:
> > > > As your X-Uptime header which could be - at least - at bit more
> > > > specific? ;-)
> >
> > > What are you getting at? ;)
> >
> > Sorry, I don't get this one. Either it's too late or I'm t
--zYM0uCDKw75PZbzx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Rocco Rutte spake thus:
> > > As your X-Uptime header which could be - at least - at bit more
> > > specific? ;-)
>=20
> > What are you getting at? ;)
>=20
27-Mar-02 at 08:09, David T-G ([EMAIL PROTECTED]) wrote :
> % > Rob 'Feztaa' Park wrote:
> % > > I don't use ps. Or any replacements.
> % >
> % > why ever not?
> %
> % Because I don't really know what it is, what it does, or why I'd ever
> % want to use it.
>
> ps is "process status" or somethi
Rob --
...and then Feztaa said...
%
% Alas! Will Yardley spake thus:
% > Rob 'Feztaa' Park wrote:
% > > I don't use ps. Or any replacements.
% >
% > why ever not?
%
% Because I don't really know what it is, what it does, or why I'd ever
% want to use it.
ps is "process status" or something li
Rob --
...and then Feztaa said...
%
% Alright, I wasn't exactly thinking when I said "all gpl", but you know
% what I mean. Everything on my system is compiled from source, it's all
% one free license or another.
We figured out what you meant when you made such a broad and fairly
unsupportable
Hi,
On Tue, Mar 26, 2002 at 12:57:23:PM -0700 Rob 'Feztaa' Park wrote:
> Alas! Rocco Rutte spake thus:
> > > A lot of people on this list and others have creative X- headers that I
> > > enjoy reading. It's just as much a part of the email as the body of the
> > > message is.
> >
> > As your X-U
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-25 14:05:45 -0700]:
>Alas! Shawn McMahon spake thus:
>> You can have it both ways; use Procmail to prepend "X-Nuke" at the
>> beginning of all the "bad" lines, then ignore X-Nuke.
>
>That br
begin quoting what Will Yardley said on Tue, Mar 26, 2002 at 07:02:10PM -0800:
>
> /home/william/procps-2.0.7/ps
> ladd% head COPYING
> GNU LIBRARY GENERAL PUBLIC LICENSE
You quoted it right there; it's not GPL, it's LGPL.
I was yanking Rob's chain, because he's an evil bast
--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Will Yardley spake thus:
> Rob 'Feztaa' Park wrote:
> > I don't use ps. Or any replacements.
>=20
> why ever not?
Because I don't really know what it is, w
Rob 'Feztaa' Park wrote:
>
> I don't use ps. Or any replacements.
why ever not? what license does the version of 'ps' you're talking about
use?
for that matter, i'm almost certain there's a GNU version of ps for all
you freakin' GNazis.
ladd% apt-get source procps
Reading Package Lists... Done
--RASg3xLB4tUQ4RcS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> begin quoting what Rob 'Feztaa' Park said on Tue, Mar 26, 2002 at 07:29:=
08PM -0700:
> > I don't use ps. Or any replacements.
On Tue, Mar 26, 2002 at 02:59:37PM -0700, Rob 'Feztaa' Park wrote:
> Alas! David T-G spake thus:
> > % Lets see you work out an x-nuke solution and we'll see how many lines it
> > % is... :P
> >
>
> [0] This officially means that every single binary on my entire system
> is GPL'd ;)
SSH, openss
begin quoting what Rob 'Feztaa' Park said on Tue, Mar 26, 2002 at 07:29:08PM -0700:
>
> I don't use ps. Or any replacements.
Ok. Do you use vim?
msg26224/pgp0.pgp
Description: PGP signature
--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> begin quoting what Rob 'Feztaa' Park said on Tue, Mar 26, 2002 at 02:59:=
37PM -0700:
> > [0] This officially means that every
begin quoting what Rob 'Feztaa' Park said on Tue, Mar 26, 2002 at 02:59:37PM -0700:
>
> [0] This officially means that every single binary on my entire system
> is GPL'd ;)
You don't have ps? What are you using instead?
msg26222/pgp0.pgp
Description: PGP signature
Alas! David T-G spake thus:
> % Lets see you work out an x-nuke solution and we'll see how many lines it
> % is... :P
>
> No, that's left as an exercise for the student. Really :-)
This student is not interested in wasting time on procmail/formail
silliness.
I've just recompiled my kernel with
Rob --
...and then Feztaa said...
%
% David, it's wakie-wakie time!
What? 42! The battle of the bulge!
%
% Alas! David T-G spake thus:
% > % That brings us back to the first problem though: How do I ignore X-Nuke
% > % without ignoring the other X- headers? (without using th
Rob --
...and then Feztaa said...
%
% Alas! David T-G spake thus:
% > Just "working" isn't enough. It has to be elegant and clever with a dash
% > of magic. *mutter* Kids these days...
%
% How is my solution not elegant? It's a simple 3 lines that trashes a
% bunch of headers that I don't wa
--xHbokkKX1kTiQeDC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! David T-G spake thus:
> Just "working" isn't enough. It has to be elegant and clever with a dash
> of magic. *mutter* Kids these days...
How is my solut
--vJguvTgX93MxBIIe
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
David, it's wakie-wakie time!
Alas! David T-G spake thus:
> % That brings us back to the first problem though: How do I ignore X-Nuke
> % without i
Alas! Rocco Rutte spake thus:
> > A lot of people on this list and others have creative X- headers that I
> > enjoy reading. It's just as much a part of the email as the body of the
> > message is.
>
> As your X-Uptime header which could be - at least - at bit more
> specific? ;-)
What are you g
Rob --
...and then Feztaa said...
%
% Alas! Shawn McMahon spake thus:
% > > That brings us back to the first problem though: How do I ignore X-Nuke
% > > without ignoring the other X- headers? (without using the huge mess
% > > david posted).
% >
% > ignore received x-n
Rob --
...and then Feztaa said...
%
% Alas! Shawn McMahon spake thus:
% > You can have it both ways; use Procmail to prepend "X-Nuke" at the
% > beginning of all the "bad" lines, then ignore X-Nuke.
%
% That brings us back to the first problem though: How do I ignore
Hi,
On Mon, Mar 25, 2002 at 02:02:17:PM -0700 Rob 'Feztaa' Park wrote:
> A lot of people on this list and others have creative X- headers that I
> enjoy reading. It's just as much a part of the email as the body of the
> message is.
As your X-Uptime header which could be - at least - at bit more
begin quoting what Rob 'Feztaa' Park said on Mon, Mar 25, 2002 at 02:34:48PM -0700:
> > ignore received x-nuke
>
> There are other headers I want to hide though.
When I said have procmail prepend all the "bad" headers, I meant "every
header you'd
--yklP1rR72f9kjNtc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> > That brings us back to the first problem though: How do I ignore X-Nuke
> > without ignoring the other X- heade
begin quoting what Rob 'Feztaa' Park said on Mon, Mar 25, 2002 at 02:05:45PM -0700:
>
> That brings us back to the first problem though: How do I ignore X-Nuke
> without ignoring the other X- headers? (without using the huge mess
> david posted).
ignore received x-nuke
--MFZs98Tklfu0WsCO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> You can have it both ways; use Procmail to prepend "X-Nuke" at the
> beginning of all the "bad"
--CNfT9TXqV7nd4cfk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> I mean, who really cares about all that other crapola?
A lot of people on this list and others have creative X- headers that I
begin quoting what Rob 'Feztaa' Park said on Mon, Mar 25, 2002 at 01:25:23PM -0700:
>
> I'd rather just rip off all the useless headers with an elegant 3-line
> procmail recipie than have to hide them all with 10 or 20 lines of
> ignore statements.
You can have it
Shawn, et al --
...and then Shawn McMahon said...
%
% If you want elegant:
%
% ignore *
% unignore date from: reply-to to cc subject list user-agent x-mailer
%
% I mean, who really cares about all that other crapola?
Well, yeah. If you want to go that far, ...
%
% Most people could go
not the people) :P
If you want elegant:
ignore *
unignore date from: reply-to to cc subject list user-agent x-mailer
I mean, who really cares about all that other crapola?
Most people could go the extra bit and snatch "user-agent" and "x-mailer"
out of there.
And you can alway
gant 3-line
procmail recipie than have to hide them all with 10 or 20 lines of
ignore statements.
> % Besides, I'm only doing it to Incredimail users. I mean, if they want to
> % accost me with tons of useless X- headers, I shouldn't have to put up w=
ith
> % them (the headers, no
Rob --
...and then Feztaa said...
%
% Alas! David T-G spake thus:
% > Rather than using procmail, which will *gasp* change the mail as it comes
% > in, just have mutt ignore those headers that you don't want to see and
% > update your list as you see new ones. To wit:
...
%
--2FkSFaIQeDFoAt0B
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! David T-G spake thus:
> Rather than using procmail, which will *gasp* change the mail as it comes
> in, just have mutt ignore those headers that you
dea. But how do I strip headers in procmail?
Rather than using procmail, which will *gasp* change the mail as it comes
in, just have mutt ignore those headers that you don't want to see and
update your list as you see new ones. To wit:
ignore "from " received content- mime-ve
--7iMSBzlTiPOCCT2k
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Rob 'Feztaa' Park spake thus:
> :0 Whf:
> * X-Mailer: IncrediMail.*
> |formail -I X-
I'm not sure if it makes much difference, but I ended up using this:
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-24 15:09:38 -0700]:
> Alas! Nicolas Rachinsky spake thus:
> > > Run stuff through sed, I suppose. I've never tried, but it should work.
> >
> > formail with -I
>
> You mean something like this at the beginning of my procmailrc:
>
> :0 Whf:
> * X
--doKZ0ri6bHmN2Q5y
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Nicolas Rachinsky spake thus:
> > Run stuff through sed, I suppose. I've never tried, but it should work.
>=20
> formail with -I
You mean something like t
Hi,
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [02-03-24 22:02]:
>Alas! Shawn McMahon spake thus:
>> begin quoting what Rob 'Feztaa' Park said on Sun, Mar 24, 2002 at
>> 01:42:09PM -0700:
>> > Maybe I could set up a hook of some kind that hides X- headers for
>> > my grandmother and nobody else?
>>
* Shawn McMahon <[EMAIL PROTECTED]> [2002-03-24 16:06:29 -0500]:
> begin quoting what Rob 'Feztaa' Park said on Sun, Mar 24, 2002 at 02:02:55PM -0700:
> >
> > Hey, that's a good idea. But how do I strip headers in procmail?
>
> Run stuff through sed, I suppose. I've never tried, but it should
Okay, did som testing (nothing thorough, mind you), and this seems
to be one of many(?) ways of doing it in Mutt.
message-hook '~f [EMAIL PROTECTED]' 'ignore x-'
message-hook '~f @' 'unignore the headers I want to see'
I guess these'll take preced
begin quoting what Rob 'Feztaa' Park said on Sun, Mar 24, 2002 at 02:02:55PM -0700:
>
> Hey, that's a good idea. But how do I strip headers in procmail?
Run stuff through sed, I suppose. I've never tried, but it should work.
msg26006/pgp0.pgp
Description: PGP signature
--L6iaP+gRLNZHKoI4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Shawn McMahon spake thus:
> begin quoting what Rob 'Feztaa' Park said on Sun, Mar 24, 2002 at
> 01:42:09PM -0700:
>
> > Maybe I could set up a hook of some
x-using people
> who have creative and interesting ones :)
:-)
> Maybe I could set up a hook of some kind that hides X- headers for my
> grandmother and nobody else?
Hmm. Would a message-hook do this? Something along the lines of
(untested):
message-hook "'~f grandma' i
begin quoting what Rob 'Feztaa' Park said on Sun, Mar 24, 2002 at 01:42:09PM -0700:
>
> Maybe I could set up a hook of some kind that hides X- headers for my
> grandmother and nobody else?
Or list all of the obnoxious ones, and then set up procmail to strip them
out; that will work as a general
the following lines in my muttrc:
> >=20
> > ignore *
> > unignore date from: reply-to to cc subject x- list user-agent
>=20
> Are you sure that the 'x-' actually works? Do you see any x-headers if
> you remove the following lines altogether?
Yes, it works. I
Look at the man page; it doesn't say anything about the order of ignore
or unignore statements. It just says "unignore" is a list of exceptions to
the "ignore" statement(s).
That's the precedence; unignores are exceptions, they take precedence over
ignor
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-24 11.15 -0700]:
> This is really weird. I have the following lines in my muttrc:
>
> ignore *
> unignore date from: reply-to to cc subject x- list user-agent
Are you sure that the 'x-' actually works? Do y
* Martin Karlsson <[EMAIL PROTECTED]> [2002-03-24 19.26 +0100]:
> * Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-24 11.15 -0700]:
> > This is really weird. I have the following lines in my muttrc:
> >
> > ignore *
> > unignore dat
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-03-24 11.15 -0700]:
> This is really weird. I have the following lines in my muttrc:
>
> ignore *
> unignore date from: reply-to to cc subject x- list user-agent
> ignore x-status x-uid x-keywords x-accept-language x-im
This is really weird. I have the following lines in my muttrc:
ignore *
unignore date from: reply-to to cc subject x- list user-agent
ignore x-status x-uid x-keywords x-accept-language x-imagebase x-fid
ignore x-mailer x-priority x-fid x-fver x-fit x-fcol x-fcat x-fdis
ignore x-extensions x-bg x
On Mon, Apr 17, 2023 at 08:52:10PM +0100, Nuno Teixeira wrote:
| Hello to all,
|
Please ignore this post. I have already sent a new and corrected one.
Thanks,
--
Nuno Teixeira
pt-quorum.com
/*
PGP Public Key:
http://www.pt-quorum.com/pgp/nunoteixeira.asc
Key fingerprint:
8C2C
Hurm, not received any mail since 02/11...
--
+---+
| Jerome De Greef | [EMAIL PROTECTED] | [EMAIL PROTECTED]|
+-+[EMAIL PROTECTED]| [EMAIL PROTECTED] |
+
On 2000-03-12 16:24:27 +0200, Mikko Hänninen wrote:
> No, they use special kind of wildcards, it's not even shell
> globbing. For them the rules are:
> - "*" is a special entry which means "all headers"
> - "something-" means that every header wh
Eugene Lee <[EMAIL PROTECTED]> wrote on Sun, 12 Mar 2000:
> So do the ignore/unignore commands deal with shell globbing only?
No, they use special kind of wildcards, it's not even shell globbing.
For them the rules are:
- "*" is a special entry which means "all
I ran into a problem with the ignore/unignore commands. It appears that
the patterns they accept cannot be regex patterns. This works:
ignore *
and this works:
unignore subject: to: from:
but this doesn't work:
unignore ^(Subject|To|From):
So do the ignore/uni
On Thu, Jan 20, 2000 at 01:06:13PM +0200, Mikko Hänninen wrote:
> Greg Matheson <[EMAIL PROTECTED]> wrote on Thu, 20 Jan 2000:
> > I'm having a problem with folder hooks in which I have (un)ignore
> > commands for From_ headers.
> I remember reading somewhere
On Thu, Jan 20, 2000 at 15:01:56 +0100, Byrial Jensen wrote:
>
> Except "unignore *" that just removes "*" from the ignore list
> if it is there, and else does nothing -- it doesn't remove all
> tokens from the ignore list as the manual says.
Ups, in fac
On Thu, Jan 20, 2000 at 17:50:03 +0800, Greg Matheson wrote:
> X-Mailer: Mutt 0.95.7us
It might help to upgrade to Mutt 1.0.1. There have been some
fixes to ignore/unignore which make them
work better.
However don't trust the manual about this topic. Header weeding
functions this wa
Greg Matheson <[EMAIL PROTECTED]> wrote on Thu, 20 Jan 2000:
> I'm having a problem with folder hooks in which I have (un)ignore
> commands for From_ headers. After unignoring the From_ header in
> one mailbox, I can't ignore it in others.
I remember reading somewhere t
I'm having a problem with folder hooks in which I have (un)ignore
commands for From_ headers. After unignoring the From_ header in
one mailbox, I can't ignore it in others. The reason I want to
see the From_ line is that I am using mutt to read my procmail
log. This file has for each
On Wed, May 19, 1999 at 01:41:48PM -0500, [EMAIL PROTECTED] wrote:
> > > unignore *
> > > ignore X-Filter In-Reply-To Autoforwarded X-UID
>
> If you simply remove the "unignore *" command, it should work the way
> you want it to..?
No. Some headers a
is doesn't seem to work:
>
> unignore *
> ignore X-Filter In-Reply-To Autoforwarded X-UID
>
>After 'unignore *', mutt seems to forget about the ignores. Am I
>doing something wrong?
You're right. It's bug in "[un]ignore" code. Due to this bug You
c
> > unignore *
> > ignore X-Filter In-Reply-To Autoforwarded X-UID
If you simply remove the "unignore *" command, it should work the way
you want it to..?
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there
owever, this doesn't seem to work:
>
> unignore *
> ignore X-Filter In-Reply-To Autoforwarded X-UID
>
> After 'unignore *', mutt seems to forget about the ignores. Am I
> doing something wrong?
Hmm. I use the inverse of that statement in my .mut
> unignore *
> ignore X-Filter In-Reply-To Autoforwarded X-UID
>
> After 'unignore *', mutt seems to forget about the ignores. Am I
> doing something wrong?
Once you unignore something, there is no way to ignore it again without
restarting mutt.
I think this is c
Hi!
First of all, thanks for developing such a great piece of software!
I am interested in seeing all the mail headers and then pruning them
down. However, this doesn't seem to work:
unignore *
ignore X-Filter In-Reply-To Autoforwarded X-UID
After 'unignore *', mutt
Hi!
First of all, thanks for developing such a great piece of software!
I am interested in seeing all the mail headers and then pruning them
down. However, this doesn't seem to work:
unignore *
ignore X-Filter In-Reply-To Autoforwarded X-UID
After 'unignore *', mutt
Please, ignore this message, just testing.
--
Un saludo,
Horacio
[EMAIL PROTECTED]
--
Quis custodiet ipsos custodet?
--
93 matches
Mail list logo
