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
{{ message }}
Repository navigation
Script manager shows scripts in lower case but sorts upper case ones first #706
Some scripts have uppercase file names and therefore are sorted before all scripts with lowercase. However, in the UI, most of them are even shown as lowercase so it's even more confusing.
I suggest to sort all scripts by name ignoring casing, so that it becomes more intuitive to find e.g. "open in explorer" in my case.
What operating system is this on? On Linux my scripts are in order. On Windows all the scripts starting with a are together but the order isn't correct. I couldn't reproduce what you show above.
Right, sorry - that's on Linux (Bazzite/Fedora), which should explain it because Windows tends to not differentiate between casing when it's about file names, while Linux does treat them separately by default.
Windows and Linux list the files in different order, and
the casing in some file names differs from the script name that is listed inside the file.
I expected this behavior:
The script names shown are the ones listed inside the files, not the file name that might be subject to character limitations or OS sorting differences.
Casing is ignored in sorting so I can find scripts quickly by name no matter if their names have capitals.
Activity
wpferguson commentedon Nov 8, 2026
What operating system is this on? On Linux my scripts are in order. On Windows all the scripts starting with a are together but the order isn't correct. I couldn't reproduce what you show above.
fblampe commentedon Nov 8, 2026
Right, sorry - that's on Linux (Bazzite/Fedora), which should explain it because Windows tends to not differentiate between casing when it's about file names, while Linux does treat them separately by default.
fblampe commentedon Nov 8, 2026
I think the cause is that:
I expected this behavior: