> -Original Message-
> From: Tim Chase [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 28, 2006 5:03 PM
>
> > When I start vim from the command line and provide a
> filename, how can
> > I prevent a default scratch buffer from also being opened?
>
> I'm not sure exactly what you mean by
On 4/29/06, Eric Crahen <[EMAIL PROTECTED]> wrote:
For some reason I get an empty hidden buffer that does show up when I
list buffers.
Must be some plugin doing this. To find which plugin is doing this,
do :scriptnames and look into your ~/.vim/plugin directory.
Also, try to start 'vim -u NONE
For some reason I get an empty hidden buffer that does show up when I
list buffers. Its the same one you'd get when you open vim w/ no
filenames. I'll poke around andd if there is a setting causing that
On 4/28/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 4/28/06, Eric Crahen <[EMAIL PROTECTED
On 4/28/06, Eric Crahen <[EMAIL PROTECTED]> wrote:
When I start vim from the command line and provide a filename, how can
I prevent a default scratch buffer from also being opened?
Vim does not create scratch buffer when you invoke it from command line
with filename. You can verify it for yours
When I start vim from the command line and provide a filename, how can
I prevent a default scratch buffer from also being opened?
I'm not sure exactly what you mean by a "default scratch
buffer".
If you supply a filename on the command line
bash$ vi file.txt
you only have one buffer
