You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
search_render() currently uses the hardcoded Notmuch::SORT_NEWEST_FIRST. I think it would be nice to make the sort order configurable for the end user, ideally on a per-search-basis. This would for example allow sorting messages tagged "inbox" oldest first, an those tagged "someothertag" newest first.
The text was updated successfully, but these errors were encountered:
We could create some kind of meta-search-term like sort:oldest-first, but then we would need to make sure it's parsed correctly everywhere and removed before sending it to libnotmuch.
Thanks for considering my suggestion. To make sure I understand your approach: Where would these meta-search-terms be specified by the end user, and how would they be mapped to particular searches?
search_render()
currently uses the hardcodedNotmuch::SORT_NEWEST_FIRST
. I think it would be nice to make the sort order configurable for the end user, ideally on a per-search-basis. This would for example allow sorting messages tagged "inbox" oldest first, an those tagged "someothertag" newest first.The text was updated successfully, but these errors were encountered: