notmuch-search-toggle-order and notmuch-tree

notmuch-search-toggle-order and notmuch-tree

[Aneesh Kumar K.V]

Hi,

I was expecting notmuch-tree to also follow the search
order(oldest-first or not). But with latest notmuch
even after i change the search order using notmuch-serach-toggle-order a
tree view always list with the default search order. Is that expected ?

-aneesh

Re: notmuch-search-toggle-order and notmuch-tree

[David Bremner]

"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:

> I was expecting notmuch-tree to also follow the search
> order(oldest-first or not). But with latest notmuch
> even after i change the search order using notmuch-serach-toggle-order a
> tree view always list with the default search order. Is that expected ?

Maybe Mark can give a more informed comment but I would say that it's
expected from a code point of view, as the tree code does not reference
the variable notmuch-search-oldest-first. This lack of control over the
display order of threads (as opposed to within the threads) does seem
like a missing feature.

d

Re: notmuch-search-toggle-order and notmuch-tree

[Mark Walters]

Hi

It is the expected behaviour, but not the desired behaviour. I posted a
series making it possible to sort oldest first in tree view at

id:1435359035-6767-1-git-send-email-markwalters1009@gmail.com

which David very kindly reviewed but then I got sidetracked and haven't
updated it. It is on my todo list, but I haven't got to it yet.

The series may well still apply: I don't know.

Note that it doesn't change the order of messages inside a thread, just
the order of the threads.

Best wishes

Mark







On Mon, 15 Aug 2016, David Bremner <david@tethera.net> wrote:
> "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> writes:
>
>> I was expecting notmuch-tree to also follow the search
>> order(oldest-first or not). But with latest notmuch
>> even after i change the search order using notmuch-serach-toggle-order a
>> tree view always list with the default search order. Is that expected ?
>
> Maybe Mark can give a more informed comment but I would say that it's
> expected from a code point of view, as the tree code does not reference
> the variable notmuch-search-oldest-first. This lack of control over the
> display order of threads (as opposed to within the threads) does seem
> like a missing feature.
>
> d