You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In your documentation you state that this plugin uses alphanumeric, but it seems to use natural sort order. That is that x7, x8 and x70, is sorted according to the number sequence of 7, 8, 70, and not the alphanumeric sequence of 7, 70, 8.
Is this a bug or a feature? And either way, would it be possible to get it to do true alphanumeric sorting?
In the image below I show the result after applying the sorting specification within my file CustomSort, and how it then doesn't show the files in alphanumeric order. Also included are the sequence of the hexadecimal numbers, 0x01FF, 0x0200 and 0x02FF, which are out of order due to the same issue. The 0x02FF is in the middle instead of at the end. Finally the image shows that the custom sort is effective (which also can be seen by file in reverse sort order outside of the SortingBug folder.
Regards,
Holroy
The text was updated successfully, but these errors were encountered:
In your documentation you state that this plugin uses alphanumeric, but it seems to use natural sort order. That is that
x7
,x8
andx70
, is sorted according to the number sequence of 7, 8, 70, and not the alphanumeric sequence of 7, 70, 8.Is this a bug or a feature? And either way, would it be possible to get it to do true alphanumeric sorting?
In the image below I show the result after applying the sorting specification within my file
CustomSort
, and how it then doesn't show the files in alphanumeric order. Also included are the sequence of the hexadecimal numbers, 0x01FF, 0x0200 and 0x02FF, which are out of order due to the same issue. The 0x02FF is in the middle instead of at the end. Finally the image shows that the custom sort is effective (which also can be seen by file in reverse sort order outside of theSortingBug
folder.Regards,
Holroy
The text was updated successfully, but these errors were encountered: