diff options
| author |  Carl Worth <cworth@cworth.org> | 2009-11-12 22:35:16 -0800 |
|---|---|---|
| committer | Carl Worth <cworth@cworth.org> | 2009-11-12 22:35:16 -0800 |
| commit | f7b49d658ad507b72d01b06d56975dba0b7cafc8 (patch) | |
| tree | 69df4deaed2a6362c449ff8df566cfeb6bea2abe /lib/query.cc | |
| parent | 5f5e9b8662d562a3d8bd9ab7144fc1fead1c3d22 (diff) | |
notmuch search: Add support for a --reverse option to reverse sort order.
Note that the difference between thread results in date order and
thread results in reverse-date order is not simply a matter of
reversing the final results. When sorting in date order, the threads
are sorted by the oldest message in the thread. When sorting in
reverse-date order, the threads are sorted by the newest message in
the thread.
This difference means that we might want an explicit option in the
interface to reverse the order, (even though the default will be to
display the inbox in date order and global searches in reverse-date
order).
Diffstat (limited to 'lib/query.cc')
| -rw-r--r-- | lib/query.cc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/query.cc b/lib/query.cc index e853d4ec..7c1df90c 100644 --- a/lib/query.cc +++ b/lib/query.cc @@ -61,7 +61,7 @@ notmuch_query_create (notmuch_database_t *notmuch, query->query_string = talloc_strdup (query, query_string); - query->sort = NOTMUCH_SORT_DATE_OLDEST_FIRST; + query->sort = NOTMUCH_SORT_DATE; return query; } @@ -123,10 +123,10 @@ notmuch_query_search_messages (notmuch_query_t *query, } switch (query->sort) { - case NOTMUCH_SORT_DATE_OLDEST_FIRST: + case NOTMUCH_SORT_DATE: enquire.set_sort_by_value (NOTMUCH_VALUE_TIMESTAMP, FALSE); break; - case NOTMUCH_SORT_DATE_NEWEST_FIRST: + case NOTMUCH_SORT_DATE_REVERSE: enquire.set_sort_by_value (NOTMUCH_VALUE_TIMESTAMP, TRUE); break; case NOTMUCH_SORT_MESSAGE_ID: |