mu find does not find matching messages

26 views
Skip to first unread message

Laurence Rochfort

unread,
Sep 27, 2016, 6:41:20 AM9/27/16
to mu-discuss
Hello,

I'm running v0.9.16, built from git.

I have found that mu isn't finding messages containing known strings. Can people please confirm I'm searching correctly?

I have a messages that contains the following string:



I search like this:

$ mu find ca-ulndev
mu: no matches for search expression (4)

I've tried various combinations of wildcards and quotes, but still get no results.

Any advice?

Cheers,
Laurence.

Jostein Berntsen

unread,
Sep 28, 2016, 4:19:43 PM9/28/16
to mu-discuss
Does mu find ca-ulndev* work?


Jostein

Laurence Rochfort

unread,
Sep 29, 2016, 4:50:42 AM9/29/16
to mu-discuss
Unfortunately not. I get exactly the same error message.

Jostein Berntsen

unread,
Sep 29, 2016, 2:01:58 PM9/29/16
to mu-discuss
Can you try this with quotes?

mu find 'ca-ulndev*'

Or else run with "--format=xquery" to check the output.


Jostein

Laurence Rochfort

unread,
Sep 30, 2016, 4:58:25 AM9/30/16
to mu-discuss
Still no results unfortunately:

~ $ mu find ca-ulndev --format=xquery
Xapian::Query((Hca_ulndev:(pos=1) OR Bca_ulndev:(pos=1) OR Cca_ulndev:(pos=1) OR Eca_ulndev:(pos=1) OR Jca_ulndev:(pos=1) OR Fca_ulndev:(pos=1) OR Mca_ulndev:(pos=1) OR Yca_ulndev:(pos=1) OR Ica_ulndev:(pos=1) OR Sca_ulndev:(pos=1) OR Tca_ulndev:(pos=1) OR Uca_ulndev:(pos=1) OR Xca_ulndev:(pos=1) OR Dca_ulndev:(pos=1) OR Gca_ulndev:(pos=1) OR Pca_ulndev:(pos=1) OR Zca_ulndev:(pos=1) OR Vca_ulndev:(pos=1) OR Wca_ulndev:(pos=1)))
~ $ mu find ca-ulndev* --format=xquery
Xapian::Query()
~ $ mu find 'ca-ulndev*' --format=xquery
Xapian::Query()

--
You received this message because you are subscribed to a topic in the Google Groups "mu-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mu-discuss/V1wIl1S7WNI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mu-discuss+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dirk-Jan C. Binnema

unread,
Oct 1, 2016, 2:52:27 PM10/1/16
to mu-di...@googlegroups.com
The search engine / query parser that mu4e uses (Xapian) treats dashes
and dots as word separators, so sadly, this is expected to not work;
there's no escaping mechanism either.

Kind regards,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

Laurence Rochfort

unread,
Oct 1, 2016, 4:41:35 PM10/1/16
to mu-di...@googlegroups.com

Thanks Dirk.

For clarification, is it dashes in just the query that cause problems, or dashes in the content too?


Dirk-Jan C. Binnema

unread,
Oct 2, 2016, 6:38:19 AM10/2/16
to mu-di...@googlegroups.com

On Saturday Oct 01 2016, Laurence Rochfort wrote:

> Thanks Dirk.
>
> For clarification, is it dashes in just the query that cause problems, or
> dashes in the content too?

Mu does a few tricks to try to get the around the limitations of the
query parser by "massaging" the content a bit when storing it (this
includes e.g. removing accents etc.), and similarly with the queries.

It's not perfect though, as you've seen.

Cheers,
Reply all
Reply to author
Forward
0 new messages