Dear Tony, Let me first thank you for your reply.
> IIUC, these lines are there so that when you start Vim as > > gvim -S > or > gvim -S mysession.vim > > the empty [No Name] buffer, which is there before Vim loads the session, > finally gets wiped out so that you don't get an additional blank window > in addition to your reloaded session. I checked what happens when the mentioned lines in the session file (see my original posting) are commented out: I got no additional empty blank window. Anyway what these lines may be good for: Skipping them has (!) an effect, namely: It removes the problem and applies the *.txt file type settings. Of course, these lines are always recreated by each :mksesseion... > A session file saves the options when you run ":mksession" and restores > then when you start "vim -S". _What_ is saved is governed by your > 'sessionoptions' setting. Yes, I use a quite limited setting already: set sessionoptions=buffers,curdir,winsize > I is quite possible to run a startup script _not_ created by > ":mksession" as a result of "vim -S". Here's my current ~/Session.vim True -- however, I sometimes use a lot of split windows, too, and entering them all manually would kind of remove the gain of sessions at all for me (besides the buffer-add commands). So, I still wonder, how to create a working session file which does not eat up my *.txt settings partly... Since it is only one single line in the sesstion file I need to skip (silent exe 'bwipe ' . s:wipebuf) I wonder why this causes problems at all? Somehow it prevents the autocommand to set the file type to *.txt. I do not see any relation. Perhaps my autocommand in my vimrc (see original posting) is incorrect? Thank You! Felix --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
