Spaces in file names will always be fiddly though. It'll work, but it'll still be wrong, because arguments are space separated, and having spaced file names totally messes with that.
Also making seitan from flour is super easy. If I could get my hands on pure gluten it would be insanely easy. Maybe not as rich in taste as soy meat, but so much cheaper than store bought meat analogues.
I know. I have nothing against the format in general, as it's plain text and will always be readable. I actually prefer it to Excel sheets, although a proper database is the nicest. It's just annoying that someone chose comma, a super commonly used punctuation mark, as default field separator for csv.
And that's totally fair, in my opinion. Speech has to flow in the language you speak, or you'll sound like an idiot. As long as people don't go around claiming to know and teaching others pronunciations for things that they themselves don't pronounce the way that was intended.
A (very well used) program I use places files in $HOME. Someone argued for changing to $XDG_CONFIG or at least add that as an option. The dev, being used to the old school way, gave the exact opposite reason: that .config was just an extra level of organization when dotfiles are what the home dir is for. So I'm not sure how successful you would be with that approach.
To be clear, I am clearly on the side of XDG, myself.
Yeah. It's a good idea to guard against it, but I would still never put spaces in filesnames that I myself choose.