Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
You're viewing a single thread.
you can also use basically anything that's not / in a file name as well, it's pretty based. Meanwhile on windows you have to use SMB mappings if you don't want your directory structure to self immolate, what a good operating system.
That's a great feature, actually, it saves you from using Windows
true my mistake, how could i forget this.
I recently renamed a few movie files to something with ':'. That worked fine on Linux, but lead to some issues on windows. With a lot of errors from next cloud for file sync and me not being able to rename them without booting back to Linux. Fun stuff
if you're using samba file sharing across OS's (like you should) you should use something called catia:mappings in order to solve that problem. It means shit like colon will be mapped to a different character, but there are some sane mappings out there that you can use.
It wasn't a file share, I have one of my drives mounted in Linux and in Windows as a general storage drive in a dualboot system
oh, that's rough. Yeah no i would still recommend using samba for that tbh.
I think you might even be able to get away with /s if you escape them properly in the filename.
Just tried. It processes the escape first and then finds the path with it. Essentially, making it look into a directory made by the characters before the \/.
The above was when I tried:
bash
echo "asd" > asd\/dsa
But then I tried using Dolphin (GUI File Browser) to make a file and:
bash
❯ ls 1 2 3 4 'asd\⁄sad.txt' ❯ ls 1 2 3 4 asd⁄sad.txt
In the first one, the backslash is not the escape character, but part of the text.
Turns out Dolphin just replaces the forward slash with U+2044 "Fraction Slash" character, hence, not requiring any escape. I'd call that cheating, but it works well.
Turns out Dolphin just replaces the forward slash with U+2044 “Fraction Slash” character, hence, not requiring any escape. I’d call that cheating, but it works well.
called it, i knew someone would use illegal characters eventually.
I would have a problem if a terminal app were to do something like this, but for GUI apps, it is expected for them to make stuff easier.
And I feel like, if you were to use a slash in a file name, it would most probably be either an "or" slash or a fraction slash, so the substitution is fine in my books.
illegal characters
Not sure about calling it that, considering it is a standard UTF-8 character. (0x2044 in UTF-16)
I would have a problem if a terminal app were to do something like this, but for GUI apps, it is expected for them to make stuff easier. And I feel like, if you were to use a slash in a file name, it would most probably be either an “or” slash or a fraction slash, so the substitution is fine in my books.
it's close enough, i generally consider an "illegal" character a non typable character. Especially these alt characters that are visually hard to distinguish from others such as the forward slash for example, i believe this was the same character used for a handful of somewhat clever phishing scams.
Seems like it's fair enough to me.
i'm not sure if you're allowed to escape the / character, i feel like it's blatantly illegal. But you could use the funny character set trolling thing instead, where you use a not forward slash instead. (not the )
I'm fairly confident MacOS allows it, I've seen people do some Utterly Cursed shit in MacOS, but idk about Linux
maybe on macos, that might be funny, it's probably fucky over there for some other reason anyway.
Im pretty sure it's just explicitly illegal in linux though.