From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 02/10] search: drop longer subject: prefix for search
Date: Fri, 9 Sep 2016 00:01:23 +0000 [thread overview]
Message-ID: <20160909000131.18584-3-e@80x24.org> (raw)
In-Reply-To: <20160909000131.18584-1-e@80x24.org>
We only document the "s:" anyways. While the long name is more
descriptive, the ambiguity makes agnostic caching (by Varnish or
similar) slightly harder and longer URLs are more likely to be
accidentally truncated when shared.
---
lib/PublicInbox/Search.pm | 1 -
t/search.t | 14 +++++++-------
2 files changed, 7 insertions(+), 8 deletions(-)
diff --git a/lib/PublicInbox/Search.pm b/lib/PublicInbox/Search.pm
index aec459b..3b25b66 100644
--- a/lib/PublicInbox/Search.pm
+++ b/lib/PublicInbox/Search.pm
@@ -58,7 +58,6 @@ my %bool_pfx_external = (
);
my %prob_prefix = (
- subject => 'S',
s => 'S', # for mairix compatibility
m => 'Q', # 'mid' is exact, 'm' can do partial
f => 'A', # for mairix compatibility
diff --git a/t/search.t b/t/search.t
index bb0861a..7abaf83 100644
--- a/t/search.t
+++ b/t/search.t
@@ -123,19 +123,19 @@ sub filter_mids {
is($res->{total}, 0, "path variant `$p' does not match");
}
- $res = $ro->query('subject:(Hello world)');
+ $res = $ro->query('s:(Hello world)');
@res = filter_mids($res);
- is_deeply(\@res, \@exp, 'got expected results for subject:() match');
+ is_deeply(\@res, \@exp, 'got expected results for s:() match');
- $res = $ro->query('subject:"Hello world"');
+ $res = $ro->query('s:"Hello world"');
@res = filter_mids($res);
- is_deeply(\@res, \@exp, 'got expected results for subject:"" match');
+ is_deeply(\@res, \@exp, 'got expected results for s:"" match');
- $res = $ro->query('subject:"Hello world"', {limit => 1});
+ $res = $ro->query('s:"Hello world"', {limit => 1});
is(scalar @{$res->{msgs}}, 1, "limit works");
my $first = $res->{msgs}->[0];
- $res = $ro->query('subject:"Hello world"', {offset => 1});
+ $res = $ro->query('s:"Hello world"', {offset => 1});
is(scalar @{$res->{msgs}}, 1, "offset works");
my $second = $res->{msgs}->[0];
@@ -181,7 +181,7 @@ sub filter_mids {
$rw_commit->();
$ro->reopen;
- # Subject:
+ # subject
my $res = $ro->query('ghost');
my @exp = sort qw(ghost-message@s ghost-reply@s);
my @res = filter_mids($res);
--
EW
next prev parent reply other threads:[~2016-09-09 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 0:01 [PATCH 0/10] search: more mairix prefix compatibility Eric Wong
2016-09-09 0:01 ` [PATCH 01/10] search: allow searching user fields (To/Cc/From) Eric Wong
2016-09-09 0:01 ` Eric Wong [this message]
2016-09-09 0:01 ` [PATCH 03/10] search: more granular message body searching Eric Wong
2016-09-09 0:01 ` [PATCH 04/10] search: fix space regressions from recent changes Eric Wong
2016-09-09 0:01 ` [PATCH 05/10] search: match quote detection behavior of view Eric Wong
2016-09-09 0:01 ` [PATCH 06/10] search: increase term positions for each quoted hunk Eric Wong
2016-09-09 0:01 ` [PATCH 07/10] search: fix compatibility with Debian wheezy Eric Wong
2016-09-09 0:01 ` [PATCH 08/10] search: avoid mindlessly calling body_set Eric Wong
2016-09-09 0:01 ` [PATCH 09/10] search: match the behavior of WWW for indexing text Eric Wong
2016-09-09 0:01 ` [PATCH 10/10] search: index attachment filenames Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160909000131.18584-3-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).