Nemo not sorting track numbers in order
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
The report identifies Nemo's track-number sorting behavior but names no source file or test. Start by reproducing the ordering with track numbers such as 10, 30, 100, and 200, then locate the sorting implementation and relevant tests; done means numeric ordering is preserved rather than lexicographic ordering.
Written by the indexing model from the issue text.
Description
I have files I'm trying to assign track numbers to, but when I set the folder to sort by track number, tracks in the 100s get sorted next to 10s, 200s next to 20s, and so on. I don't want track 200 to come before track 30. Not sure if this is a bug or oversight or what, but how do I get it to sort by numerical value?
- Dominant language
- C
- Stars
- 487
- Forks
- 171
- Avg merge
- 10d 19h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/nemo-extensions
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
linuxmint/nemo-extensions#592 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
linuxmint/nemo-extensions#588 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
linuxmint/nemo-extensions#587 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
linuxmint/nemo-extensions#586 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linuxmint/nemo-extensions#585 · 1 comment ·
All issues in linuxmint/nemo-extensions
Similar issues
-
rc_runtime_activate_richpresence leaves a half-initialised entry when the buffer allocation failsOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
RetroAchievements/rcheevos#558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
libsdl-org/SDL#16464 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
chore(gateway): emit INFO budget reserved/settled logs for proactivity v2 (chip task_2855f4ec)Possibly taken A pull request linked to this issue is open or already merged. Openbackend
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BasedHardware/omi#20940 ·
Maintainers usually reply within 1 day