From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: How to combine spam-split with Subject filtering.
Date: Thu, 13 Jan 2005 16:04:47 +0100 [thread overview]
Message-ID: <86mzvd9xps.fsf@mat.ucm.es> (raw)
In-Reply-To: <16870.34083.953155.509283@parhasard.net>
>>>>> "Aidan" == Aidan Kehoe <kehoea@parhasard.net> writes:
Aidan> Ar an triú lá déag de mà Eanair, scrÃobh Uwe Brauer:
>> So does isearch-forward-regexp behaves differently from
>> putting this string in a function which uses a regexp search???
Aidan> Yes; if you think about it, when you put a string in a
Aidan> function, you need to do string escaping for characters
Aidan> like \ and ", whereas for isearch-forward-regexp thereâs
Aidan> no need for the string escaping, because no string literal
Aidan> is involved.
Aidan> So typing M-C-s \[POSIBLE SPAM\] RET does the same regexp
Aidan> match as does M-: (re-search-forward "\\[POSIBLE SPAM\\]"
Aidan> nil t) RET . Some variation on this latter is better for
Aidan> building regexps youâre going to use in a program, in my
Aidan> experience.
Ok, now doing
M-: (re-search-forward "\\[POSIBLE SPAM\\]" nil t)
in a spam group which contains a message with this subject, finds this
message. However putting
("Subject" "\\[POSIBLE SPAM\\]" "SPAM.POSS")
into nnimap-split-fancy function, does not find this message that is
it is passed to the next entry the spam-split function.
I tried to run edebug on nnimap-split-fancy, but nothing useful came
out.
I am really puzzled, is there somewhere a bug?
Uwe
next parent reply other threads:[~2005-01-13 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86zmzeqwcs.fsf@mat.ucm.es>
[not found] ` <m2r7kqggr7.fsf@Stella-Blue.local>
[not found] ` <v97jmhhhcg.fsf@marauder.physik.uni-ulm.de>
[not found] ` <864qhlr4n0.fsf@mat.ucm.es>
[not found] ` <866521cyr5.fsf@mat.ucm.es>
[not found] ` <16870.34083.953155.509283@parhasard.net>
2005-01-13 15:04 ` Uwe Brauer [this message]
2005-02-08 19:24 ` Ted Zlatanov
2005-02-10 18:16 ` Uwe Brauer
2005-02-10 18:15 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86mzvd9xps.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).