Fixes #871 It is valid - though odd - to open a file at `some//path`. In that case the current check for fugitive buffers matches and changes &path unexpectedly. A stricter match against `://` prevents this.
