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

RFE: secondary sort criterion #1215

Closed
backerman opened this Issue Mar 30, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@backerman

backerman commented Mar 30, 2018

Expected or desired behavior

I would like to be able to sort headers by multiple criteria; e.g., by sender and then timestamp.

Actual behavior

Only one sort criterion can be selected; the sort is not stable, so messages with an identical value of the new criterion are ordered essentially randomly.

Steps to reproduce

  1. Open a header view.
  2. Sort by any criterion.
  3. Sort by a different criterion. Observe that the sort is not stable.

Versions of mu, mu4e/emacs, operating system etc.

Arch, Emacs 25.3, Linux 4.15.13-1 (standard Arch package), mu/mu4e 1.0 release.

Additional information

Should the sort not being stable be a separate issue?

@djcb

This comment has been minimized.

Show comment
Hide comment
@djcb

djcb Jun 11, 2018

Owner

Would be useful, but this is sadly rather hard to implement, since the underlying Xapian database does not support it, and we can't really do it on the client (emacs) side without things becoming much slower.

Xapian doing the sorting also means that the query is re-run, making the sort order unstable.

So, unfortunately will have to decline this.

Owner

djcb commented Jun 11, 2018

Would be useful, but this is sadly rather hard to implement, since the underlying Xapian database does not support it, and we can't really do it on the client (emacs) side without things becoming much slower.

Xapian doing the sorting also means that the query is re-run, making the sort order unstable.

So, unfortunately will have to decline this.

@djcb djcb closed this Jun 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment