William Casarin <jb55@jb55.com> writes: > > > I'm adding a few new keys (from, subject, etc). I don't want to > duplicate them in the old notmuch_sort_t enum, I assume to move to the > new API there should be something like this as well? It's been a while since I was thinking about this, but I suspect my intent was that new keys could be supported (only) by the new API. We basically want to deprecate the old API as soon as the new one exists to transition to. > > > Then we could eventually do something like: > > --sort date:desc,from:asc > > Which would mean: sort by date, and then by from. I think the "notmuch way" would be to spell out descending and ascending, and rely on completion to make that less painful to type. I only mention it because I was confused by what "desc" and "asc" stood for. For some reason descriptor and ascii jumped to my pre-caffeinated mind. > Perhaps it could do something sensible by default without order > qualifiers as well: > > --sort date,from I would hope so, yes. _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch