Earlier quoted context omitted.
There's a server at work that name with a non-ascii character. I've run into compatibility issues lots of times where I can't connect. I prefer to just use English with ASCII and be happy
Server names are different. They are by and large machine-facing identifiers, whereas filenames have a 50-50 split of whether they are machine-facing, human-facing, or both. They makes their support of Unicode a much more critical (and appealing) proposition.
I'm “still afraid to use spaces in file names” years old
811–817 of 817 posts
Re: I'm “still afraid to use spaces in file names” years old
#812My username has been my name which has an accented character and has broken countless Windows apps every year since forever, so I just keep a C:/Programs folder where I run stuff. You should never not fear filenames.
Re: I'm “still afraid to use spaces in file names” years old
#813Let me tell you how much of a pain in the ass that my employer forces spaces in the corporate OneDrive directory. PS-Microsoft is horrible about stupidly named folders being created and dumped in there.
Re: I'm “still afraid to use spaces in file names” years old
#814Earlier quoted context omitted.
Too many characters on Linux? Quite difficult to reach to be fair. Do you have an example?
I have been trying to repro with a small nodejs server but either the server cut off the content-disposition filename or firefox truncates it. When I get that in the wild I'll post an update. In the meantime: $ touch 11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111…
Re: I'm “still afraid to use spaces in file names” years old
#815Earlier quoted context omitted.
I have been trying to repro with a small nodejs server but either the server cut off the content-disposition filename or firefox truncates it. When I get that in the wild I'll post an update. In the meantime: $ touch 11111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111111…
But it's _per file name_. The path could be waaay longer than Windows' one
Re: I'm “still afraid to use spaces in file names” years old
#816I have an overly-aggressive function in my .bashrc to rename all files in the current directory: # Rename all files in a directory rn() { rename "s/ /-/g" * rename "s/_/-/g" * rename "s/–/-/g" * rename "s/://g" * rename "s/\(//g" * rename "s/\)//g" * rename "s/\[//g" * rename "s/\]//g" * rename 's/"//g' * rename "s/'//g" * rename "s/,//g" * rename "y/A-Z/a-z/" * rename "s/---/--/g" * rename "s/---/--/g" * } I use th…
Word of warning from hard experience: rn is a really dangerous thing to name a function because it is one char away from rm.