Daniel P. Berrange schrieb:
Oh and if you want to be really nice, you could say that any filename
with a leading '/' is implicitly file:///, since I can't imagine
any protocol name starting with a '/'. And this would ensure any
existing usage with absolute filenames 'just works' without tripping
up on colons.
Existing usage would mean to get an error message. I don't see any
reason why we should change this behaviour if we have a real solution.
Adding more exceptions to the guessing doesn't really make it more
harmless.