Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: gnus-summary-respool-trace for nnimap?
Date: Wed, 21 Nov 2001 13:40:01 +0100	[thread overview]
Message-ID: <vaf1yiscn6m.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uy9l0jt4i.fsf@axis.com> (Niklas Morberg's message of "Wed, 21 Nov 2001 11:49:49 +0100")

Niklas Morberg <niklas.morberg@axis.com> writes:

> I'm having some very weird problems with my
> nnimap-split-fancy rules which I need to locate (when
> checking a from address not containing any numbers against
> the regex ".*[0-9]\\{2,\\}.*" it will incorrectly match,
> probably because the from address contains the character
> `ö', but I don't know).

If you do C-u g on the message, what do you see?  Maybe the ö is QP
encoded, as "=F6", which contains a digit...

But OTOH, that doesn't contain two or more digits.  Hm.  But maybe
the QP encoding has a leader like "=?iso-8859-1", which does contain
digits.

FWIW, I think you can replace ".*[0-9]\\{2,\\}.*" with
".*[0-9][0-9].*".

And the two ".*" are only needed because fancy splitting adds
invisible "\\<" and "\\>" around your regexp.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



  reply	other threads:[~2001-11-21 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 10:49 Niklas Morberg
2001-11-21 12:40 ` Kai Großjohann [this message]
2001-11-21 13:33   ` Niklas Morberg
2001-11-21 15:31     ` Kai Großjohann
2001-11-21 15:58       ` Matching split rules against decoded headers? (Was: Re: gnus-summary-respool-trace for nnimap?) Niklas Morberg
2001-11-21 16:33         ` Kai Großjohann
2001-11-21 18:43       ` gnus-summary-respool-trace for nnimap? Paul Jarc

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=vaf1yiscn6m.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    /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).