Hacker News Reader

No the author is saying the opposite. They expect file9.txt to be after file10.txt, but it many modern operating systems, it isn’t!

View on HN

Really, I do not know how I missed that :) I read it a couple of times to and I still thought he wanted it the other way.

So my original comment kind of stands but in a opposite way.

I have never see file_9.txt sorted before file_10.txt, I just tested it on OpenBSD and I got this, which I have always seen:

$ ls|sort

file_1.txt

file_10.txt

file_12.txt

file_2.txt

file_20.txt

file_3.txt

file_9.txt

Author here - My surprise stems exactly from the fact that for the last few years I have exclusively managed my files via a the UNIX shell, which behaves in the classical way.

When I started using Linux as my daily driver after many years of Windows (but with familiarity with UNIX systems going way back), I knew it would be like that in the terminal, but it still took some adjustment. But actually, Nemo does the same "natural sort" thing, and also sorts case-insensitively.

Reply on news.ycombinator.com