Consider: Assume you have an existing file, file.a
gvim -N -u NONE :e file.a (make some changes to the buffer, but do not save) :new :split file.a This will correctly re-use the (modifed) buffer for file.a. Exit Vim. Restart in the same way: gvim -N -u NONE :e file.a (make some changes to the buffer) :split file.a (this causes E37 as discussed in another thread) :split! file.a (this abandons the changes to file.a, reloading the file instead of re- using the buffer) I think this is incorrect behavior (why should the behavior of :split file depend on the buffer it is called from?) but at the very least the help for :split_f should say that it reloads the buffer. Except, it only reloads the buffer when called from the same buffer you are using as an argument. If called from any other buffer, it re-uses an existing buffer. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
