I prefer if :bdelete does not fail in this situation even if there is no <bang> (!). Changing it so that the command fails without <bang> looks like a change that breaks scripts and plugins because :bdelete currently fails only when the buffer has modifications. What's the reason to make it fail when the buffer is not modified?
The whole point of fixing a buffer in a window with winfixbuf is to make sure that no other buffer takes the place (window) of the buffer. But if the buffer is being intentionally deleted by the user then it means it is not needed in that place (or anywhere else) anymore. The situation is similar as with doing :bdelete for a buffer in a tab that has no other window. Vim closes it's window and even removes the whole tab. It does not make the command fail just because there is no <bang>. Is there any reason to handle :bdelete of a winfixbuf-ed buffer differently? Thinking about possible solutions: How about just closing the window? Or is there a way to change winfixbuf option so that it does not only say which buffer is fixed to the window but also says what happens with the window when the buffer becomes deleted? And by the way: But then: What happens when the fixed buffer is going to be hidden? -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/3180debc-697d-4612-bf5f-763846885537n%40googlegroups.com.
