John Beckett wrote: > bill lam wrote: >> On second thought, my requirement seemed faulty in that all >> buffers except the current should already be written >> otherwise it can not be switched, Is this correct? >> >> If the current buffer has unsaved modification, Tim's >> function gives warning and aborted. Why are such warning >> when it is supposed to delete other_ buffers? > > I guess that Tim assumes ':set hidden' which should be pretty > standard for experienced Vim users. The default (nohidden) means > Vim won't go off and fiddle with another buffer while the > current buffer is unsaved (that is the safest, and easiest to > understand for users).
Actually, my assumption had been that the current buffer had been saved, and was thus safe to leave. An alternative would be to prefix the whole mess with ":sp" to clone the current window/buffer into a new buffer. Then, when done, you can close the window. That will keep the current buffer open without the need to save or be 'hidden' during the operation. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
