On Mon, Jun 18, 2007 at 02:05:59PM +0100, James Vega wrote: > I'm able to confirm this. I'm looking into the cause now.
Looking at the netrw plugin, this seems like intentional behavior. I'll email upstream to see if there's a way he can have file:// behave like the other read methods. The typical "file://path/to/file" isn't too bad (2 buffers instead of one) but "file://localhost/path/to/file" is a bit distracting since it creates 3 buffers -- one for the URI, one for "localhost/path/to/file" (as well as a message about new directory), and one for the actual file. James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
