Skip to content

Doc tree, backlinks, tags and templates ignores case when sorting alphabetically by name #8360

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

Closed
RobertBJTU opened this issue May 25, 2023 · 0 comments
Assignees
Milestone

Comments

@RobertBJTU
Copy link

RobertBJTU commented May 25, 2023

a modest proposal: when the textbook sorting rules is by name alphabetically, it is more natural when it is case-insensitive

In what scenarios do you need this feature?

The current sorting rules are: in the order of ASCII codes, uppercase first, lowercase later. It's a bit too programmer, most users want to see is not case-sensitive.

Change the first letter to lowercase, and the sorting will change immediately. Non-programmers will be very confusing at the sorting results.

e.g. bat, json should occur much earlier than Node.js
image

Describe the optimal solution

Take the most general option, like VS Code, case-insensitive when sorting by name alphabetically,

Describe the candidate solution

No response

Other information

No response

@88250 88250 self-assigned this May 26, 2023
@88250 88250 changed the title a modest proposal: when the textbook sorting rules is by name alphabetically, it is more natural when it is case-insensitive Doc tree ignores case when sorting alphabetically by name May 26, 2023
@88250 88250 changed the title Doc tree ignores case when sorting alphabetically by name Doc tree, backlinks, tags, templates ignores case when sorting alphabetically by name May 26, 2023
@88250 88250 changed the title Doc tree, backlinks, tags, templates ignores case when sorting alphabetically by name Doc tree, backlinks, tags and templates ignores case when sorting alphabetically by name May 26, 2023
@88250 88250 added this to the 2.8.10 milestone May 26, 2023
88250 added a commit that referenced this issue May 26, 2023
@88250 88250 closed this as completed May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants