On Fri, 16 Nov 2007 16:10:40 +0100, Vladimir Marek <[EMAIL PROTECTED]> wrote:
> I do have > > :set shell=/bin/sh > > This just says to vim, to use /bin/sh for executing external commands. > It does not say which shell I should use for my interactive work. > > Then I run > > :!fish > > Welcome to fish, the friendly interactive shell > Type help for instructions on how to use fish > [EMAIL PROTECTED] ~> echo $version > 1.22.3 > [EMAIL PROTECTED] ~> > > And I do have fish shell. > > Now the problem is, when I exit > > [EMAIL PROTECTED] ~> exit > > Good bye > > [1]+ Stopped vi > > It somehow stops vim. When I bring it to foreground (using fg), vi > continues normally. I've seen something similar using recent versions of zsh. When I start a zsh subshell from Vim and then exit the shell, Vim bombs out with a message about being unable to read its input. I tried to work out what was happening but had trouble understanding how a child process could influence its parent in that way. In the end I gave up and "fixed" the problem by using an older version of zsh (3.1.9). -- Matthew Winn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
