QuazarOmega

Yes, that does sound reasonable

Well yes, we use double quotes as you said, it may be annoying, but not difficult, sanitization is another matter.
I actually don't remember of any terminal application that has issues with that, that's why I made the original question

Edit: I understood now why you mentioned sanitization, double quotes shouldn't be an issue because in filenames they are forbidden by the OS usually, that's on the user if they try

Unpopular opinion maybe, but that's just called bad programming.
For strictly code we can't use spaces obviously, user input, on the other hand, should be handled gracefully always, not doing so is like those platforms that only supported ASCII even after the international userbase was already very prominent because the devs were just too lazy to update their systems to use Unicode (Windows is still like that with Powershell I discovered recently... shudders)

I don't disagree, though I think they're just a very minor annoyance that is easily adjusted with double quotes and tab autocompletion.
Personally I prefer to use spaces for many user facing files, like documents and images/media

Curious, where was the dot as separator for torrents born? Some kind of software limitation?

Thanks for tips ! I'll be needing that

Damn, respect for that ~~shit~~stuff.
Do you have some suggestions for fiber rich foods too?

Oh thanks, didn't know there was a Qt counterpart, it looks pretty good!

Lol, I should have had you at solarized

Indeed, how else will everyone see my glorious solarized light theme?

Ah that's annoying, so as I understand it should just be down to having persistent sink and routing right? Not sure if this what you want as I haven't tried, but could this thread be helpful?