Hello, I have a similar problem (if not the same) as in "session problem" topic from March 7. When a few files are open in tabs LOCALLY, a session is saved and later restored, everything is ok. But if the command to open one of the files comes from outside (--remote-silent- tab) one gets error "E163: There is only one file to edit" when trying to restore the session. Here is how to reproduce the problem:
$ echo a > a.txt $ echo b > b.txt $ gvim --noplugin -u NONE -U NONE :e a.txt $ gvim --noplugin -u NONE -U NONE --remote-silent-tab b.txt :mksession! :qa $ gvim --noplugin -u NONE -U NONE -S :messages " E163 There is only one file to edit One can avoid controlling vim from outside and create a session file issuing local commands only: $ gvim --noplugin -u NONE -U NONE :e a.txt :tab new :e b.txt :mksession! :qa $ gvim --noplugin -u NONE -U NONE -S " everything ok - good session file The bad session file sets up an arg list with one arg only, but later tries to edit a file on the second place in args (2argu) and that's the line where the error message comes. The good session doesn't use arglist at all (wipes it even with argdel *). I didn't find any help file mentioning that an argument list is set when vim is issued a command via --remote-silent-tab. My vim is 7.2.49. Does anybody have an idea how to fix the session creation? Thanks, Tom -- You received this message from the "vim_use" 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
