On Tue, May 26, 2009 at 12:37 PM, Tim Chase wrote: > >> I think the culprit is >> >> C:\Programmi\Vim\vimfiles\after\ftplugin\help.vim >> >> which contains the line >> >> wincmd o > > wow. Yeah, that would do it. I'm not sure what was desired when > creating this, but it looks like some add-on filetype rather than > one that comes with the stock build of Vim. But I'm boggled by > the apparent bogosity. :) > >> That's the reason why I don't get the window split when I press <F1>. Is >> there the possibility that when I press <F1>, the file isn't saved or at >> least have the possibility of undoing or is it better to get rid of >> ..\after\ftplugin\help.vim? > > Since the stuff in the after\ directory should be user-controlled > (rather than vim-distribution-controlled), you should be able to > nuke or edit the file with impunity. I'd just blow away that > line unless you smell other bad mojo in the > after\ftplugin\help.vim file in which case you should be able to > just nuke the file.
What he said, and also... you would still be able to undo in the old file despite this if you used :set hidden. The best summary I can give of what the 'hidden' option does is this: By default, whenever a buffer will no longer be displayed in any windows, it must first be saved, and then will be forgotten about. The 'hidden' option changes this behavior. It lets you keep a file open and unsaved, even when it isn't still being displayed, and lets you keep undo and redo history when you come back to that file. This makes working with multiple files much more pleasant. Don't worry, though - Vim will force you to either save the buffer or choose to throw it away before it will let you exit. 'hidden' is definitely an option that I would recommend that everyone set in his vimrc. ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
