ChatGPT解决这个技术问题 Extra ChatGPT

How do I close a single buffer (out of many) in Vim?

I open several files in Vim by, for example, running

vim a/*.php

which opens 23 files.

I then make my edit and run the following twice

:q

which closes all my buffers.

How can you close only one buffer in Vim?

Note that you can open the files in separate Vim windows using vim -o a/*.php (or -O to use vertical windows) and avoid the buffer navigation - this is a great method for only a few files, but with 23 files they'll only have a few lines/columns each.
@Jefromi: Thank you for pointing that out! I have never use the option -o before.
On the subject of window splits. If you are already in Vim and want to open another file in a split :esp for horizontal :evsp for vertical.

i
ib.

A word of caution: “the w in bw does not stand for write but for wipeout!”

More from manuals:

:bd

Unload buffer [N] (default: current buffer) and delete it from the buffer list. If the buffer was changed, this fails, unless when [!] is specified, in which case changes are lost. The file remains unaffected.

If you know what you’re doing, you can also use :bw

:bw

Like |:bdelete|, but really delete the buffer.


Also the possibility of doing ':M,Nbd' to close buffer numbers M to N. Or ':bd N1 N2...' where N# is a buffer number
The manual says to only use :bw if "you know what you're doing", which I don't, so I guess I'll use :bd.
w is short for write command according to Vim manual, there is furthermore no mention of any "wipeout". The description of the command (help write) starts with "Write the whole buffer to the current file."
@amn by using :help bw you will see bw is stand for wipe.
@amn I got confused too, but he meant the w in the bw command means wipeout he is not talking about the w command. He put this warning there so people did not think the bw command meant buffer write (which it does not it means buffer wipeout.)
R
RedBlueThing

If this isn't made obvious by the the previous answers:

:bd will close the current buffer. If you don't want to grab the buffer list.


Before finding :bd it never made any sense to me that people had no problems doing a :ls -> scan for doc number -> unload buffer by number. Do people actually find this effective?
@svend for a range of buffers sure, but for a lone one a :bd is probably more effective.
:bd only closes the buffer whereas (whatever that means) whereas :bw will also clear all the variables and REALLY eliminates it from the ls buffer.
n
nightingale2k1

Check your buffer id using :buffers

you will see list of buffers there like

1  a.php
2  b.php
3  c.php

if you want to remove b.php from buffer

:2bw

if you want to remove/close all from buffers

:1,3bw

You can also wipe all buffers with :%bw
short cut to check buffer id: 2 CTRL-G
g
guv'

Rather than browse the ouput of the :ls command and delete (unload, wipe..) a buffer by specifying its number, I find that using file names is often more effective.

For instance, after I opened a couple of .txt file to refresh my memories of some fine point.. copy and paste a few lines of text to use as a template of sorts.. etc. I would type the following:

:bd txt <Tab>

Note that the matching string does not have to be at the start of the file name.

The above displays the list of file names that match 'txt' at the bottom of the screen and keeps the :bd command I initially typed untouched, ready to be completed.

Here's an example:

doc1.txt doc2.txt
:bd txt 

I could backspace over the 'txt' bit and type in the file name I wish to delete, but where this becomes really convenient is that I don't have to: if I hit the Tab key a second time, Vim automatically completes my command with the first match:

:bd doc1.txt

If I want to get rid of this particular buffer I just need to hit Enter.

And if the buffer I want to delete happens to be the second (third.. etc.) match, I only need to keep hitting the Tab key to make my :bd command cycle through the list of matches.

Naturally, this method can also be used to switch to a given buffer via such commands as :b.. :sb.. etc.

This approach is particularly useful when the 'hidden' Vim option is set, because the buffer list can quickly become quite large, covering several screens, and making it difficult to spot the particular buffer I am looking for.

To make the most of this feature, it's probably best to read the following Vim help file and tweak the behavior of Tab command-line completion accordingly so that it best suits your workflow:

:help wildmode

The behavior I described above results from the following setting, which I chose for consistency's sake in order to emulate bash completion:

:set wildmode=list:longest,full

As opposed to using buffer numbers, the merit of this approach is that I usually remember at least part of a given file name letting me target the buffer directly rather than having to first look up its number via the :ls command.


k
kenorb

Use:

:ls - to list buffers

:bd#n - to close buffer where #n is the buffer number (use ls to get it)

Examples:

to delete buffer 2: :bd2


Y
Yi Jiang

You can map next and previous to function keys too, making cycling through buffers a breeze

map <F2> :bprevious<CR>
map <F3> :bnext<CR>

from my vimrc


W
Wolfson

Close buffer without closing the window

If you want to close a buffer without destroying your window layout (current layout based on splits), you can use a Plugin like bbye. Based on this, you can just use

:Bdelete (instead of :bdelete)
:Bwipeout (instead of :bwipeout)

Or just create a mapping in your .vimrc for easier access like

:nnoremap <Leader>q :Bdelete<CR>

Advantage over vim's :bdelete and :bwipeout

From the plugin's documentation:

Close and remove the buffer. Show another file in that window. Show an empty file if you've got no other files open. Do not leave useless [no file] buffers if you decide to edit another file in that window. Work even if a file's open in multiple windows. Work a-okay with various buffer explorers and tabbars.

:bdelete vs :bwipeout

From the plugin's documentation:

Vim has two commands for closing a buffer: :bdelete and :bwipeout. The former removes the file from the buffer list, clears its options, variables and mappings. However, it remains in the jumplist, so Ctrl-o takes you back and reopens the file. If that's not what you want, use :bwipeout or Bbye's equivalent :Bwipeout where you would've used :bdelete.


Thanks, this is exactly what I want, and it also works well with coc-explorer. :)
S
Santi

How about

vim -O a a

That way you can edit a single file on your left and navigate the whole dir on your right... Just a thought, not the solution...


L
Leonid Shevtsov

[EDIT: this was a stupid suggestion from a time I did not know Vim well enough. Please don't use tabs instead of buffers; tabs are Vim's "window layouts"]

Maybe switch to using tabs?

vim -p a/*.php opens the same files in tabs

gt and gT switch tabs back and forth

:q closes only the current tab

:qa closes everything and exits

:tabo closes everything but the current tab


Why do you say that using tabs is a stupid suggestion? I only ask because I use tabs all the time... :^/
@Nate: I decided to elaborate on that leonid.shevtsov.me/en/…
That was a great post - it inspired me to dig even deeper - have you looked at wildmenu? It's similar to lustyjuggler (though simpler) but it's built in (which was good for me, because lustyjuggler needs +ruby, and the default vim for ubuntu oneiric ships -ruby).
@Nate: yep, I'm using wildmenu to open files, but when you have many files in the project, it just doesn't scale. Also, the vim-nox package from Ubuntu has Ruby support.
N
New Alexandria

Those using a buffer or tree navigation plugin, like Buffergator or NERDTree, will need to toggle these splits before destroying the current buffer - else you'll send your splits into wonkyville

I use:

"" Buffer Navigation                                                                                                                                                                                        
" Toggle left sidebar: NERDTree and BufferGator                                                                                                                                                             
fu! UiToggle()                                                                                                                                                                                              
  let b = bufnr("%")                                                                                                                                                                                        
  execute "NERDTreeToggle | BuffergatorToggle"                                                                                                                                                              
  execute ( bufwinnr(b) . "wincmd w" )                                                                                                                                                                      
  execute ":set number!"                                                                                                                                                                                    
endf                                                                                                                                                                                                        
map  <silent> <Leader>w  <esc>:call UiToggle()<cr>   

Where "NERDTreeToggle" in that list is the same as typing :NERDTreeToggle. You can modify this function to integrate with your own configuration.


for this, the bbye plugin is perfect which preserves your window layout when using :bdelete or :bwipeout. See my answer.