On Linux file systems you can use any character except NULL, and / is a reserved character.

E.g. on ext-4 "All characters and character sequences permitted, except for NULL ('\0'), '/', and the special file names "." and ".." which are reserved for indicating (respectively) current and parent directories."

In filenames? AMATEURS! Use obscure Unicode in your passphrases for maximum security. Ctrl-Shift-U, enter arbitrary code point, bam! 🦊 Works even better with a Compose key and a nice, chonky .XCompose file to throw some gr∑∑k letters around, for instance, like some confused script kiddie. :)

On topic: There are multiple variants of spaces in Unicode. You're welcome, and now go and create something utterly deranged with that information.

unix filenames are just string of bytes, the operating system does not interpret it in anyway. this is a much saner approach compared to Windows where language settings can change file system behavior.

I'm just gonna pretend I didn't hear that.

⏰️.🪵

ChatGPT is taking notes

10 seconds of googling indicates this is true for Windows and Mac as well. I haven't looked specifically, but I'd be a little surprised if it wasn't true for Android and iOS as well.

But really, why would they add rules to prevent people from using certain unicode codepoints in filenames? Should they disallow Klingon as well? Kanji? Of course not. Emojis are codepoints just like U+0061 is.

Of course there are good reasons to disallow things like newlines and forward slashes in Linux filenames, but what specifically would even be the argument for preventing emojis?

It's all just Unicode

You can have emoji as your WiFi network name too

Kinda interesting to see what older devices do when faced with such a network

Same for Windows (11): I just renamed a file to an apple emoji

You can use emojis for variable names in swift code.

what is even more funny about this is that the name of that directory used to be locale-dependent, so in sweden it was just called "Program", completely nullifying that idea.

Given even what little I know of their history and what they are doing now, I cannot be sure this wasn't the intention at least partially

'I don't know what you mean, I've never encountered any annoyances.'

"inverted commas"? single quotes?

I tried to parse the first one but got all confused because there's no closing single quote.

If it fucking works...

Sometimes it does. But not always.

Hyphens > underscores for filenames because all web standards prefer hyphens so if you ever want to network your files its a much smoother experience!

This is the best for tab completion, altho I prefer hyphens visually

I prefer lowercase with hyphens, but I'm transitioning into a team that does everything camelCase, which is the second best case, but I still strongly dislike it.

I mean, at least in Bash tools like ls do use quotes by default:

$ ls
 filename_without_space  'filename with space'

But yeah, tab expansion uses backslashes, sadly.

Because quoting requires token expansion (e.g. ~ to /home/you). Escaping gives you a much shorter path in that case.

That said I'm with you, full quoted paths read better to me.

Just put the whole thing in quotes. You might have to escape extra sets of quotes, usually with a backslash.

Yep, exactly. And tab. \ is weird at first but makes sense if you think about it

Rust made me have an habit of using snake_case... .rs

sveltekit is beautiful (thanks for spreading the word)

One of the fun things about modern Windows is that ~1 shit still appears every once in a rare while. Gotta love just stacking more and more shit on top of ancient systems in the name of backwards compatibility!

I think you're misremembering a little. Long filenames was introduced in Win95.

Yea, Win 3.1 didn't support long names - that came with Win95. Win 3.1 was a shell on DOS.

But I understand - it all blends together after um... 40 years (ouch!).

i think i am old

https://youtube.com/watch?v=UzqcNlhaqIY