Skip to content
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

Don't perform alphabetical sort in listcategory. #2888

Merged
merged 1 commit into from Aug 8, 2017

Conversation

rcorre
Copy link
Contributor

@rcorre rcorre commented Aug 5, 2017

Instead, expect the data to be given in the desired order. Completion
functions should sort their data if they want it sorted in the
completion. This has a few implications:

Note that prefix-based filter sorting is still performed, so items
starting with the filter pattern come first.


This change is Reviewable

@The-Compiler
Copy link
Member

I suppose this also fixes #2354. 😉

Instead, expect the data to be given in the desired order. Completion
functions should sort their data _if_ they want it sorted in the
completion. This has a few implications:

- {book,quick}marks appear in the same order they do in the text file.
  This means users can rearrange their mark files for custom sorting.
  Fixes qutebrowser#2354
- Sessions are sorted as they appear in the session manager
- Tabs are sorted numerically, not alphabetically (Fixes qutebrowser#2883)

Note that prefix-based filter sorting is still performed, so items
starting with the filter pattern come first.
@rcorre
Copy link
Contributor Author

rcorre commented Aug 6, 2017

Yup, just referenced that in the commit message. Also a geolocation test is broken but it doesn't appear to be my fault 😁

@The-Compiler
Copy link
Member

81b2609 hopefully helps with the geoclue error - I already had it fixed in the new-config branch but not in master.

@The-Compiler The-Compiler merged commit 6e025c1 into qutebrowser:master Aug 8, 2017
@The-Compiler
Copy link
Member

Thanks! I also added sorting for the sessions in a20f017 (as they'd just be randomly ordered based on how they're stored on disk).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tab numbers are ordered alphabetically with new completion
3 participants