On Sun, 18 Apr 2010 15:56:58 +0200, "Sebastian Spaeth" wrote:
> > The patches do:
> > 1: Introduce NOTMUCH_SORT_UNSORTED
> > 2: Introduce notmuch search --sort=unsorted
> > 3: Make notmuch tag not sort results by date
> >
> > #2 is the one I am least sure about, I don't know if there is a use
On Sun, 18 Apr 2010 15:56:58 +0200, Sebastian Spaeth sebast...@sspaeth.de
wrote:
The patches do:
1: Introduce NOTMUCH_SORT_UNSORTED
2: Introduce notmuch search --sort=unsorted
3: Make notmuch tag not sort results by date
#2 is the one I am least sure about, I don't know if there is a
On 2010-04-16, Sebastian Spaeth wrote:
> Olly was right in that even for "notmuch tag" we were sorting the
> results by date before applying tag changes. I have slightly reworked my
> patch to have notmuch tag avoid doing that. I also split up the patch in
> 3 patches that do one thing each.
>
>
On 2010-04-15, Olly Betts wrote:
> > I would be happy to have it called --sort=relevance too, the unsorted
> > points out potential performance improvements a bit better, IMHO
> > (although they seem to be really small with a warm cache).
>
> When using the results of a search to add/remove
On Fri, Apr 16, 2010 at 08:37:04AM +0200, Sebastian Spaeth wrote:
> On 2010-04-15, Olly Betts wrote:
> > Also, sorting by relevance requires more calculations and may require
> > fetching additional data (document length for example).
> >
> > So I think it would make sense for --sort=relevance
On 2010-04-15, Olly Betts wrote:
I would be happy to have it called --sort=relevance too, the unsorted
points out potential performance improvements a bit better, IMHO
(although they seem to be really small with a warm cache).
When using the results of a search to add/remove tags,
On Fri, Apr 16, 2010 at 08:37:04AM +0200, Sebastian Spaeth wrote:
On 2010-04-15, Olly Betts wrote:
Also, sorting by relevance requires more calculations and may require
fetching additional data (document length for example).
So I think it would make sense for --sort=relevance and
Sebastian Spaeth writes:
> On 2010-04-14, Jason White wrote:
> > > Also add a --sort=unsorted command line option to notmuch search to test
> > > this.
> >
> > Does this provide relevance-ranked search results? I think relevance ranking
> > is the Xapian default if a sort order isn't specified.
Sebastian Spaeth writes:
On 2010-04-14, Jason White wrote:
Also add a --sort=unsorted command line option to notmuch search to test
this.
Does this provide relevance-ranked search results? I think relevance ranking
is the Xapian default if a sort order isn't specified.
Yes, by
Sebastian Spaeth wrote:
> previously we were always sorting the returned results by some string value,
> but sometimes we might just be interested in the number of results, and don't
> need any sorting.
>
> Also add a --sort=unsorted command line option to notmuch search to test this.
Does this
On 2010-04-14, Jason White wrote:
> > Also add a --sort=unsorted command line option to notmuch search to test
> > this.
>
> Does this provide relevance-ranked search results? I think relevance ranking
> is the Xapian default if a sort order isn't specified.
Yes, by default it is using
previously we were always sorting the returned results by some string value,
but sometimes we might just be interested in the number of results, and don't
need any sorting.
Also add a --sort=unsorted command line option to notmuch search to test this.
A search that matches 1200 messages, returns
previously we were always sorting the returned results by some string value,
but sometimes we might just be interested in the number of results, and don't
need any sorting.
Also add a --sort=unsorted command line option to notmuch search to test this.
A search that matches 1200 messages, returns
On 2010-04-14, Jason White wrote:
Also add a --sort=unsorted command line option to notmuch search to test
this.
Does this provide relevance-ranked search results? I think relevance ranking
is the Xapian default if a sort order isn't specified.
Yes, by default it is using
14 matches
Mail list logo
