From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: nnimap-split-fancy: regexp ".*" matches less than expected
Date: Mon, 09 Apr 2018 20:14:33 -0400 [thread overview]
Message-ID: <87efjn3ok6.fsf@uwo.ca> (raw)
In-Reply-To: <87vad1le8z.fsf@gmail.com>
On Apr 8, 2018, Chris Marusich <cmmarusich@gmail.com> wrote:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>> On Apr 06 2018, Chris Marusich <cmmarusich@gmail.com> wrote:
>>
>>> This is the same as before, but I've replaced "gnucash-user" with ".*".
>>> I expected the same result as before, but Gnus surprised me. Instead,
>>> gnus-summary-respool-query says:
>>>
>>> This message would go to list.user
>>>
>>> and gnus-summary-respool-trace says:
>>>
>>> ("cc" "\\(.*\\)@gnucash.org" "list.\\1")
>>> "list.\\1"
>>>
>>> In this case, why does the ".*" match "user" instead of "gnucash-user"?
>>
>> I think that happens because the actual regexp used for searching is
>> "\\(\\(FIELD\\):.*\\)\\<\\(VALUE\\)\\>", note the embedded ".*".
>
> I've tried to figure out a good way to accomplish what I want, but I'm
> stuck.
Does it help to put a literal space character at the start of your
regexp, like " \\(.*\\)@gnucash.org"?
I'm not sure what "\\<" and "\\>" are doing in the constructed regexp,
but if they are matching literal "<" and ">" characters, then this
probably won't work.
Dan
prev parent reply other threads:[~2018-04-10 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 6:08 Chris Marusich
2018-04-07 9:09 ` Andreas Schwab
2018-04-07 17:03 ` Chris Marusich
2018-04-07 18:31 ` Andreas Schwab
2018-04-08 18:55 ` Chris Marusich
2018-04-08 19:49 ` Andreas Schwab
2018-04-10 0:14 ` Dan Christensen [this message]
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=87efjn3ok6.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).