Tmpfs Adding Case Insensitive Support For Wine / Steam Play & Flatpaks

[usta]

Back in the day I learned via Windows archives that XFCE has a really badass batch renaming tool built into Thunar. Damn I miss that batch rename ability and I wish KDE had it.

Hello , i am a bit away from the tool which you used in xfce , is kde's own batch renamer tool not enough ? I mean this one : ( on website it looks like not got any new updates but actually it already ported to Qt6 )

https://apps.kde.org/krename/

[smitty3268]

The number of times in my life that I've really wanted a bunch of files in a folder with the same name but different casing has been zero.

Agreed, and if you have two files with the same name but different casing it just causes confusion about which one you really want.

The only reason to have case-sensitivity is to make the FS simpler/more efficient, since it doesn't have to worry about any kind of locale specific rules when converting.

[pieman]

That's pretty funny coming from the person not capitalizing words . I prefer sensitivity ... until I'm on Linux and I extract an archive created on Windows with things named using a combination of CaMeL CaSe, ALL CAPS, all lower, and EveRy 0tH3r Fuck3d up way under the sun. We clearly have our own biases on this subject , though I do agree about it having little benefit for the vast majority of normal users.

Back in the day I learned via Windows archives that XFCE has a really badass batch renaming tool built into Thunar. Damn I miss that batch rename ability and I wish KDE had it.

this drove me mad a few years ago when i was manually installing mods for fallout new vegas. i was amazed at how many alterations for folders like "nvdlc0*" people had it named as "NVdlc03" or "nVDLc03" and then things like the basic folders like "textures" some would be "Textures," "textures," "TEXTURES" and such.

[toves]

An Mac's HFS file system is another surprise too. By default case preserving but case insensitive.

Got nasty surprise many years ago when I reinstalled MacOSX 10.4 on a powerbook opting to try the UFS file system (essentially BSD' Unix's fast file system FFS.)

While a UFS system volume was an option, and it did boot, the case sensitivity of UFS screwed a lot of the OS system processes as to be pretty much irremediable.

Personally I prefer to think of names in file systems purely as sequences of bytes (octets) so by implication case sensitive.

Files etc under *ix are fundamentally inodes (vnodes) which might go by one or more names (labels.) I imagine quite small tweaks to the name-to-inode lookup process could push the problem out to user space.

I imagine not all natural language scripts, typefaces etc have cases - I cannot imagine Chinese ideograms having the concept. Even languages that use different character representations depending on its position in the word or even in the sentence pose the question of how much of the user's language's syntax and punctuation rules ought to be encoded in a file system?

[ahrs]

The number of times in my life that I've really wanted a bunch of files in a folder with the same name but different casing has been zero.

Yet this is exactly what you get when you don't force people to be case-sensitive. skeevy420 already mentioned the problem with archives, this is a huge issue with game mods because nobody forces any consistency. On Windows, it will extract to the Data, data, or DaTA folder, but on Linux they will be separate directories. It's impossible to deal with this situation too, should an archiver attempt to normalise it how should they do that? All lowercase? Title case? Something else? It's much better when file and directory names just mean what they say they are.

[Quackdoc]

Yet this is exactly what you get when you don't force people to be case-sensitive. skeevy420 already mentioned the problem with archives, this is a huge issue with game mods because nobody forces any consistency. On Windows, it will extract to the Data, data, or DaTA folder, but on Linux they will be separate directories. It's impossible to deal with this situation too, should an archiver attempt to normalise it how should they do that? All lowercase? Title case? Something else? It's much better when file and directory names just mean what they say they are.

the amount of times I have run a script, compiled something, tried to open a file, only to get no file available, because of case issues, is absurdly high. I once had to spend an entire day going through a project created by a primarily windows developer, because all references to the code had capitalization dependent on the circumstances of the code/build scripts, but all files/folders were lowercase.

like wise, I recently got my parents onto linux, and had to turn documents folder to case insensitive because when they save files by name, or open them by name, sometimes they use capitalization, sometimes they don't, and this is actually a large issue for them.

[skeevy420]

Hello , i am a bit away from the tool which you used in xfce , is kde's own batch renamer tool not enough ? I mean this one : ( on website it looks like not got any new updates but actually it already ported to Qt6 )

https://apps.kde.org/krename/

It actually seems like it does more than the XFCE one. The one with XFCE comes with Thunar. I guess I really meant Thunar and Dolphin more than XFCE and KDE.

[mobadboy]

It's funny because windows is basically Linux now, but with a couple of ad trackers on top. But WHY are these idiots, of all things, taking the trash case insensitive filesystem to Linux?? Will /bin become /BiN???? please tell me this has already been nacked, jesus

[mobadboy]

An Mac's HFS file system is another surprise too. By default case preserving but case insensitive.

Got nasty surprise many years ago when I reinstalled MacOSX 10.4 on a powerbook opting to try the UFS file system (essentially BSD' Unix's fast file system FFS.)

While a UFS system volume was an option, and it did boot, the case sensitivity of UFS screwed a lot of the OS system processes as to be pretty much irremediable.

Personally I prefer to think of names in file systems purely as sequences of bytes (octets) so by implication case sensitive.

Files etc under *ix are fundamentally inodes (vnodes) which might go by one or more names (labels.) I imagine quite small tweaks to the name-to-inode lookup process could push the problem out to user space.

I imagine not all natural language scripts, typefaces etc have cases - I cannot imagine Chinese ideograms having the concept. Even languages that use different character representations depending on its position in the word or even in the sentence pose the question of how much of the user's language's syntax and punctuation rules ought to be encoded in a file system?

APFS is actually the default filesystem for a while.

[oiaohm]

me arms and wrists hurt too much to bother with capitalization , once I finally find a useful speech to text tool for linux, I'll have some of the best capitalization AND punctuation on here assuming the tool is good lol.

And end up doing 4 times as much correction work as speech to text finds creative ways to stuff you over.

https://flathub.org/apps/net.mkiol.SpeechNote

There are some quite good speech to text options for Linux Quackdoc but all of them have the issue of all the traps of English.

I did professional dictation work at one point using the court reporters machine. So I learnt all the creative stuff-ups even a human could end up with and it be English.language not exact being at fault. Hopefully you are not setting your speech to text bar unreasonably high.