-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable sort order when displaying search results #21
Comments
We could create some kind of meta-search-term like Does that sound like a reasonable solution? |
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? |
For example something like this: let g:notmuch_folders = [
\ [ 'lkml', 'tag:inbox and folder:lkml/ sort:newest-first' ],
\ [ 'to-do', 'tag:to-do sort:oldest-first' ],
\ ] |
Looks reasonable to me. Additionally, I suggest adding a configuration option for the default sorting order, for convenience. |
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: