Re: [vile] Invoking vile on non-existent files

[Decklin Foster]

Paul Fox writes:

> the latter behavior -- loading them from within the editor -- is
> entirely expected.  vile assumes that if you move away from an
> empty, unmodified buffer that represents a non-existent file,
> that you made a typo, and that you probably don't want that
> buffer.  e.g., if you typed "vile mkaefile", and then ":e
> makefile", then by design it will discard the buffer called
> "mkaefile".

That's true. What actually happened to me was I made a bunch of
directories and wanted to edit foo/index.html, bar/index.html, etc., at
once. So I'd like to have that work, but I don't mind implicitly killing
any buffer I might create in the "mkaefile" case. Figured it might have
something to do with why the other case was happening, though.

(On the other hand, would it necessarily hurt if the original, empty
buffer were left there? I'd probably save and quit the correct
"makefile" without stopping to think about "mkaefile"'s continued
existence. I only mention this in case it would be difficult to fix the
one behavior (argv) without changing the other (:e). But if people are
used to the latter maybe it should be left intact.)

-- 
things change.
address@hidden