From: ellie <el@horse64.org>
To: musl@lists.openwall.com
Subject: [musl] A journey of weird file sorting and desktop systems
Date: Fri, 28 Jan 2022 14:41:38 +0100 [thread overview]
Message-ID: <f3e60c55-c20e-ef67-8098-3e285abbc01e@horse64.org> (raw)
After spending a bit wondering why files like "elder1" and "Elder2" end
up at completely different spots in the file list on my postmarketOS
(=Alpine-based) system, I filed a ticket with the Nemo file manager.
Turns out Nemo just uses locale-dependent sorting, so I spent an hour
trying to set LC_COLLATE to fix this, until I stumbled across the remark
on musl's website that LC_COLLATE sorting is simply not supported. So I
seem to be stuck with this, which I did not expect.
This to me seems kind of disastrous on a desktop system. I just fail to
see any average default user (who doesn't know ASCII in their head)
expecting "elder1" and "Elder2" to be miles apart in a sorted listing
even as a default US person, let alone in some other language that may
be expected to use a different sorting for whatever reason. (This
affects umlauts too, I assume? So that'd be most European languages
having file lists entirely messed up, too.) The sorting shouldn't be
stuck as something that just makes sense to programmers and balks at any
special vowels, and it appears at least as of now there is just no way
to fix this.
Should desktop file managers like Nemo not be using this sorting
function? Or is musl not intended for desktop use, and postmarketOS
should switch? Otherwise, it seems like this omission in musl seems like
kind of a big deal. Or is it really just me who is constantly confused
as to where any file is at in any file lists...?
Or in other words, would be kind of cool if this could be changed
next reply other threads:[~2022-01-28 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 13:41 ellie [this message]
2022-01-28 14:10 ` Rich Felker
2022-01-28 14:57 ` ellie
2022-01-28 16:58 ` enh
2022-01-28 18:01 ` Rich Felker
2022-01-28 18:33 ` enh
2022-01-28 19:22 ` Rich Felker
2022-01-28 19:47 ` Markus Wichmann
2022-01-28 18:01 ` Ariadne Conill
2022-01-28 17:54 ` Ariadne Conill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3e60c55-c20e-ef67-8098-3e285abbc01e@horse64.org \
--to=el@horse64.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).