>his path contains space
>>60480610
>*path with space blocks you're path*
>>60480856
i fuck the space between characters with my penis
>>60481232
So that is how wide it is, eh?
>>60481270
yes, i have a noodle diccu desu
>>60480610
Explain plz
I'm a windows user
>>60484035
Linux users have severe hatred of paths with spaces because software reliant on command line interfaces can't handle it well. Same issue sometimes with slashes and reverse slashes. And different line endings on documents.
>>60484085
And different line endings on documents.
No that one is not a problem when you use correct tools.
>>60484085
Thanks for responding in a cordial manner
>>60480610
I can sort of understand situations where you want spaces, but newlines?
That guy deserves to loose all files he ever created.
never an issue since I know how press \, ", and Tab.
>>60484085
Honestly its not that bad just use tab to autocomplete desu.
>>60484085
>reverse slashes
Wonderful.
>>60484085
free software quality
>"\\\path\\\to\\\folder\\\poo.php"
>>60484035
A typical C application looks something like this:int main(int argument_count, char *argument_vector[]){
return 0;
}
You give the application a list of arguments and they are separated by spaces.
You can escape the sequence, so it is not a huge problem anymore.
>>60484085
slashes cannot be in filenames on windows or gnu/linux, On gnu/linux, you use / for directory change and \ for escaping chars where windows accidentally used \ to indicate directories and when they changes it to /, it was too late, so now they use both.
Line endings is usually either \n or \r\n
It is only a problem on windows as gnu/linux applications have fixed that shit decades ago.
>>60485110
>php
>>60485252
Line endings is not a problem on Windows too.
>>60485268
It's the sort of garbage you expect to find when you have to use \\\
>>60485308
It is sort of.
Windows does not have an easy way to install software so a lot of people use defaults like notepad to open text files or excel to open csv files.
>>60485371
And those two programs are perfectly fine with Windows eol.
>>60484085
My Windows 10(TM) LTSB (TM) installation doesn't have this problem. (i made a macfag joke am i cool yet??)