2009/4/19 jrray <[email protected]>: >> Vim returns a non-zero exit code when there was any error while editing. >> This is because of Posix compatibility. However, this should only >> happen when in Ex mode, thus using "vim -e" or after "Q". It's unclear >> why it would happen when starting vim and using ":q" from Normal mode. >> I can't reproduce it. > > This happens to me on 10.5.6 (vim 7.2.22). > > Running "vim", searching for a non-existent string "/asdf<CR>", then > quitting ":q<CR>" will produce an exit code of 1. > > For some reason this only happens when I run "vim", and not "/usr/bin/ > vim". > > Here's a shell log of me doing the above steps with the two different > process names: > > octopus:~ jrray$ vim || echo failed > failed > octopus:~ jrray$ /usr/bin/vim || echo failed > octopus:~ jrray$ which vim > /usr/bin/vim > > This continues to happen after I move my ~/.vim dir and ~/.vimrc file > out of the way.
Interesting. Thanks for find that out. Now I see why my "svn commit" always has this strange failure. It seems I can at least use "export EDITOR=/usr/bin/vim" as a workaround, before the root cause is identified. -- Wu Yongwei URL: http://wyw.dcweb.cn/ --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
