From: Ruthard Baudach <ruthard.baudach@web.de>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] Strangeness in search syntax
Date: Sat, 02 May 2015 12:22:21 +0200 [thread overview]
Message-ID: <1430561884-sup-6859@ruthard-lappi> (raw)
In-Reply-To: <fe7dd94b-49bf-4495-a5b6-591ede08a6ba@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 4083 bytes --]
Greetings back,
This is not sup, but xapian related.
Xapian (www.xapian.org) draws its power from stemming and indexing the
documents it is fed, thus only being able to find what it's stemmer
considers to be a "word".
I'm not a xapian expert -- only played a bit with it -- but unless there
are some deeply buried settings in the xapian API to add brackets to
xapian's concept of a word, it's not possible to distinguish [SECURITY]
and SECURITY.
By the way, this would not be the sup way to do it anyhow. We've got
labels, so the thing to do would be to set up a before-add-message hook
to autolabel incomming email from Debian with subject [SECURITY], and
search for `label:debian AND label:security`
Or simply search for
`from:debian-security-announce@lists.debian.org AND subject:security`
(and label them with debsec or so for faster access -- this address is
so long!)
Regards,
Ruthard
>== Auszüge aus der Nachricht von Michael Parks vom 2015-04-30 11:14:
> Greetings all,
>
> I've noticed something interesting when trying to do searches against
> specific message fields. As an example, I'm signed up to the Debian
> security advisories list, and those are all tagged with a "[SECURITY]" in
> the subject line. Getting sup to retrieve these messages, and only these
> messages, has proven to be problematic.
>
> Specifically, it appears as if the brackets are ignored. If I run a full
> query for:
>
> subject:"[SECURITY]"
>
> ..I also get other messages which have the word "security" in the subject
> lines. Similar searches which return identical results include:
>
> subject: [SECURITY]
> subject:[SECURITY]
> subject:\[SECURITY\]
> subject: \[SECURITY\]
> subject:"\[SECURITY\]"
>
> ..none of which result in the desired search behavior. It's as if the
> brackets are being silently ignored.
>
> I just wanted to ask and make sure I'm not doing something silly before
> opening a bug on this :)
>
> --M
>
> Greetings all,
>
> I've noticed something interesting when trying to do searches against
> specific message fields. As an example, I'm signed up to the Debian
> security advisories list, and those are all tagged with a "[SECURITY]" in
> the subject line. Getting sup to retrieve these messages, and only these
> messages, has proven to be problematic.
>
> Specifically, it appears as if the brackets are ignored. If I run a full
> query for:
>
> subject:"[SECURITY]"
>
> ..I also get other messages which have the word "security" in the subject
> lines. Similar searches which return identical results include:
>
> subject: [SECURITY]
> subject:[SECURITY]
> subject:\[SECURITY\]
> subject: \[SECURITY\]
> subject:"\[SECURITY\]"
>
> ..none of which result in the desired search behavior. It's as if the
> brackets are being silently ignored.
>
> I just wanted to ask and make sure I'm not doing something silly before
> opening a bug on this :)
>
> --M
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Sup email client" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [1]supmua+unsubscribe@googlegroups.com.
> To post to this group, send email to [2]supmua@googlegroups.com.
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/supmua/fe7dd94b-49bf-4495-a5b6-591ede08a6ba%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:supmua+unsubscribe@googlegroups.com
> 2. mailto:supmua@googlegroups.com
> 3. https://groups.google.com/d/msgid/supmua/fe7dd94b-49bf-4495-a5b6-591ede08a6ba%40googlegroups.com?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
--
Dr. Ruthard Baudach
Speckertsweg 36a
97209 Veitshöchheim
----
Emails bitte verschlüsseln und signieren.
Meine PGP-Id: 0xAC5AC6C2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-05-02 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 18:14 Michael Parks
2015-05-02 10:22 ` Ruthard Baudach [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=1430561884-sup-6859@ruthard-lappi \
--to=ruthard.baudach@web.de \
--cc=supmua@googlegroups.com \
/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